@peerbit/program
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@peerbit/any-store-interface | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@peerbit/pubsub | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@peerbit/keychain | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@peerbit/pubsub-interface | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@peerbit/time | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@peerbit/blocks | AI (dependencies): First-party sibling package in the peerbit monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/pubsub | AI (phantom-deps): Same-org monorepo dep; declared for type resolution, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@peerbit/libp2p-test-utils | AI (phantom-deps): Same-org monorepo dep; declared for type resolution, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@peerbit/blocks | AI (phantom-deps): Same-org monorepo dep; declared for type resolution, not a phantom risk. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 6.0.31 | 16 / 1 | |
| 6.0.30 | 17 / 0 | |
| 6.0.29 | 17 / 0 | |
| 6.0.28 | 17 / 0 | |
| 6.0.27 | 17 / 0 | |
| 6.0.26 | 17 / 0 | |
| 6.0.25 | 17 / 0 | |
| 6.0.24 | 17 / 0 | |
| 6.0.23 | 17 / 0 | |
| 6.0.22 | 17 / 0 | |
| 6.0.21 | 17 / 0 | |
| 6.0.20 | 17 / 0 | |
| 6.0.19 | 17 / 0 | |
| 6.0.18 | 17 / 0 | |
| 6.0.17 | 17 / 0 | |
| 6.0.16 | 17 / 0 | |
| 6.0.15 | 17 / 0 | |
| 6.0.14 | 17 / 0 | |
| 6.0.13 | 17 / 0 | |
| 6.0.12 | 17 / 0 | |
| 6.0.11 | 17 / 0 | |
| 6.0.10 | 17 / 0 | |
| 6.0.9 | 17 / 0 | |
| 6.0.8 | 17 / 0 | |
| 6.0.7 | 17 / 0 | |
| 6.0.6 | 17 / 0 | |
| 6.0.5 | 17 / 0 | |
| 6.0.4 | 17 / 0 | |
| 6.0.3 | 17 / 0 | |
| 6.0.2 | 17 / 0 | |
| 6.0.1 | 17 / 0 | |
| 6.0.0 | 17 / 0 | |
| 5.6.3 | 17 / 0 | |
| 5.6.2 | 17 / 0 | |
| 5.6.1 | 17 / 0 | |
| 5.6.0 | 17 / 0 | |
| 5.5.2 | 17 / 0 | |
| 5.5.1 | 17 / 0 | |
| 5.5.0 | 17 / 0 | |
| 5.4.5 | 17 / 0 | |
| 5.4.4 | 17 / 0 | |
| 5.4.3 | 17 / 0 | |
| 5.4.2 | 17 / 0 | |
| 5.4.1 | 17 / 0 | |
| 5.4.0 | 17 / 0 |
v6.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.