@peerbit/pubsub
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:any-signal | AI (phantom-deps): Test/config-only reference in peerbit monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@multiformats/multiaddr | AI (phantom-deps): Test/config-only reference in peerbit monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@libp2p/tcp | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:it-pushable | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:uint8arrays | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@dao-xyz/borsh | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@libp2p/crypto | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:it-pipe | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@libp2p/websockets | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:it-length-prefixed | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@libp2p/circuit-relay-v2 | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@peerbit/any-store-interface | AI (phantom-deps): Same org scope; config/test reference; stable false positive for this monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 408 versions; no provenance is the norm for this package. | ai | |
| phantom-deps | phantom-dep:@libp2p/identify | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:p-defer | AI (phantom-deps): Config/test file reference only; stable pattern for this monorepo package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 5.2.11 | 22 / 1 | |
| 5.2.10 | 22 / 1 | |
| 5.2.9 | 22 / 1 | |
| 5.2.8 | 22 / 1 | |
| 5.2.7 | 22 / 1 | |
| 5.2.6 | 22 / 1 | |
| 5.2.5 | 22 / 1 | |
| 5.2.4 | 22 / 1 | |
| 5.2.3 | 22 / 1 | |
| 5.2.2 | 22 / 1 | |
| 5.2.1 | 22 / 1 | |
| 5.2.0 | 22 / 1 | |
| 5.1.6 | 22 / 1 | |
| 5.1.5 | 22 / 1 | |
| 5.1.4 | 22 / 1 | |
| 5.1.3 | 22 / 1 | |
| 5.1.2 | 22 / 1 | |
| 5.1.1 | 22 / 1 | |
| 5.1.0 | 22 / 1 | |
| 5.0.8 | 22 / 1 | |
| 5.0.7 | 22 / 1 | |
| 5.0.6 | 22 / 1 | |
| 5.0.5 | 22 / 1 | |
| 5.0.4 | 22 / 1 | |
| 5.0.3 | 22 / 1 | |
| 5.0.2 | 22 / 1 | |
| 5.0.1 | 22 / 1 | |
| 5.0.0 | 22 / 1 | |
| 4.1.4 | 22 / 1 | |
| 4.1.3 | 22 / 1 | |
| 4.1.2 | 22 / 1 | |
| 4.1.1 | 22 / 1 | |
| 4.1.0 | 22 / 1 |
v5.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.