@peerbit/proxy
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:libp2p | AI (phantom-deps): libp2p is a peer/re-export dependency in peerbit ecosystem packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@peerbit/blocks | AI (phantom-deps): Same-org package used as re-export or type dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@peerbit/pubsub | AI (phantom-deps): Same-org package used as re-export or type dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@peerbit/stream | AI (phantom-deps): Same-org package used as re-export or type dependency; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Active peerbit ecosystem package with 402 versions; missing repo/README polish is cosmetic, not indicative of spam. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 5.4.14 | 20 / 1 | |
| 5.4.13 | 20 / 1 | |
| 5.3.11 | 20 / 1 | |
| 5.3.8 | 4 / 1 | |
| 5.3.7 | 4 / 1 | |
| 5.3.6 | 4 / 1 | |
| 5.3.5 | 4 / 1 | |
| 5.3.3 | 4 / 1 | |
| 5.3.2 | 4 / 1 | |
| 5.3.1 | 4 / 1 | |
| 5.3.0 | 4 / 1 | |
| 5.2.26 | 4 / 1 | |
| 5.2.25 | 4 / 1 | |
| 5.2.24 | 4 / 1 | |
| 5.2.23 | 4 / 1 | |
| 5.2.22 | 4 / 1 | |
| 5.2.21 | 4 / 1 | |
| 5.2.20 | 4 / 1 | |
| 5.2.18 | 4 / 1 | |
| 5.2.17 | 4 / 1 | |
| 5.2.16 | 4 / 1 | |
| 5.2.15 | 4 / 1 | |
| 5.2.14 | 4 / 1 | |
| 5.2.13 | 4 / 1 |
v5.4.14
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.
v5.4.13
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.
v5.3.11
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.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.