@zauru-sdk/config
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
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 2 | |
| 2.32.0 | 0 / 1 | |
| 2.23.1 | 0 / 1 | |
| 2.19.0 | 0 / 1 | |
| 2.0.220 | 0 / 1 | |
| 2.0.100 | 0 / 1 | |
| 2.0.87 | 0 / 1 | |
| 2.0.83 | 0 / 1 | |
| 2.0.73 | 0 / 1 | |
| 2.0.0 | 0 / 1 |
v2.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.