@stamp-lib/stamp-example-catalog
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency; phantom-dep false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 5 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.1 | 5 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.9 | 5 / 0 | |
| 0.7.8 | 5 / 0 | |
| 0.7.7 | 5 / 0 | |
| 0.7.6 | 5 / 0 | |
| 0.7.5 | 5 / 0 | |
| 0.7.4 | 5 / 0 | |
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.4 | 5 / 0 | |
| 0.6.3 | 5 / 0 | |
| 0.6.2 | 5 / 0 | |
| 0.6.1 | 5 / 0 | |
| 0.6.0 | 5 / 0 |
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.