@google-cloud/secret-manager
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
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 1 / 14 | |
| 6.2.0 | 1 / 14 | |
| 6.1.3 | 1 / 14 | |
| 6.1.2 | 1 / 15 | |
| 6.1.1 | 1 / 15 | |
| 6.1.0 | 1 / 15 | |
| 6.0.1 | 1 / 15 | |
| 6.0.0 | 1 / 15 |
v6.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.