@zowe/db2-for-zowe-cli
IBM® Db2® Plug-in for Zowe CLI
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ibm_db | AI (dependencies): ibm_db is the canonical IBM Db2 native binding; expected and intentional dependency for this plugin. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.1.12 | 1 / 23 | |
| 6.1.11 | 1 / 23 | |
| 6.1.10 | 1 / 23 | |
| 6.1.9 | 1 / 23 | |
| 6.1.8 | 1 / 23 | |
| 6.1.7 | 1 / 23 | |
| 6.1.6 | 1 / 23 | |
| 6.1.5 | 1 / 23 | |
| 6.1.4 | 1 / 23 | |
| 5.0.21 | 1 / 28 | |
| 5.0.20 | 1 / 28 |
v6.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.