@peerbit/indexer-cache
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:@peerbit/time | AI (phantom-deps): Same-org dep declared but may be transitively used; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.11 | 4 / 1 | |
| 0.2.10 | 4 / 1 | |
| 0.2.9 | 4 / 1 | |
| 0.2.8 | 4 / 1 | |
| 0.2.7 | 4 / 1 | |
| 0.2.6 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.0 | 4 / 1 | |
| 0.0.1 | 3 / 1 |
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.