@peerbit/any-store
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid declared as runtime dep; referenced in config/indirect usage; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/time | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on build tooling patterns, not a real import gap. | ai | |
| phantom-deps | phantom-dep:@peerbit/crypto | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/logger | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/build-assets | AI (phantom-deps): Same-org monorepo build tooling dep; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.2.9 | 10 / 2 | |
| 2.2.8 | 10 / 2 | |
| 2.2.5 | 10 / 2 | |
| 2.2.1 | 10 / 2 | |
| 2.1.16 | 10 / 2 | |
| 2.1.14 | 7 / 1 | |
| 2.1.13 | 7 / 1 | |
| 2.1.12 | 7 / 1 | |
| 2.1.11 | 7 / 1 | |
| 2.1.10 | 7 / 1 |
v2.2.8
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: marcus.pousette.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.