@cabloy/deps
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of cabloy monorepo; mass-production and sparse metadata are expected for this publisher's ecosystem packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.1.8 | 0 / 2 | |
| 1.1.5 | 0 / 0 | |
| 1.1.4 | 0 / 0 | |
| 1.1.3 | 0 / 2 | |
| 1.1.2 | 0 / 2 | |
| 1.1.1 | 0 / 2 | |
| 1.0.20 | 0 / 0 | |
| 1.0.19 | 0 / 0 | |
| 1.0.18 | 0 / 0 | |
| 1.0.17 | 0 / 0 | |
| 1.0.15 | 0 / 0 | |
| 1.0.12 | 0 / 2 | |
| 1.0.11 | 0 / 2 | |
| 1.0.9 | 0 / 0 | |
| 1.0.8 | 0 / 0 | |
| 1.0.7 | 0 / 0 | |
| 1.0.4 | 0 / 0 |
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.