@google-cloud/containeranalysis
Containeranalysis client for Node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Google Cloud Node.js client libraries do not currently publish Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.8.0 | 2 / 14 | |
| 6.7.2 | 2 / 14 | |
| 6.7.1 | 2 / 15 | |
| 6.7.0 | 2 / 15 | |
| 6.6.0 | 2 / 15 | |
| 6.5.0 | 2 / 15 | |
| 6.4.0 | 2 / 15 |
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.