@peerbit/test-utils
Test utils for Peerbit
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:it-pushable | AI (phantom-deps): Test-utils package; deps may be re-exported or used indirectly in test helpers. | ai | |
| phantom-deps | phantom-dep:@libp2p/interface | AI (phantom-deps): Type-level or indirect usage common in test utility packages within peerbit monorepo. | ai | |
| phantom-deps | phantom-dep:libsodium-wrappers | AI (phantom-deps): Crypto dependency likely used transitively or in test setup helpers. | ai | |
| phantom-deps | phantom-dep:@multiformats/multiaddr | AI (phantom-deps): Multiaddr used in network test helpers; may be re-exported rather than directly imported. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @peerbit/* packages; not a per-version concern. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 3.0.35 | 17 / 2 | |
| 3.0.34 | 17 / 2 | |
| 3.0.33 | 17 / 2 | |
| 3.0.32 | 17 / 2 | |
| 3.0.31 | 17 / 2 | |
| 3.0.30 | 17 / 2 | |
| 3.0.29 | 17 / 2 | |
| 3.0.28 | 17 / 2 | |
| 3.0.27 | 17 / 2 | |
| 3.0.26 | 17 / 2 | |
| 3.0.25 | 17 / 2 | |
| 3.0.24 | 17 / 2 | |
| 3.0.23 | 17 / 2 | |
| 3.0.22 | 17 / 2 | |
| 3.0.21 | 17 / 2 | |
| 3.0.20 | 17 / 2 | |
| 3.0.19 | 17 / 2 | |
| 3.0.18 | 17 / 2 | |
| 3.0.17 | 17 / 2 | |
| 3.0.16 | 17 / 2 | |
| 3.0.15 | 17 / 2 | |
| 3.0.14 | 17 / 2 | |
| 3.0.13 | 17 / 2 | |
| 3.0.12 | 17 / 2 | |
| 3.0.11 | 17 / 2 | |
| 3.0.10 | 17 / 2 | |
| 3.0.9 | 17 / 2 | |
| 3.0.8 | 17 / 2 | |
| 3.0.7 | 17 / 2 | |
| 3.0.6 | 17 / 2 | |
| 3.0.5 | 17 / 2 | |
| 3.0.4 | 17 / 2 | |
| 3.0.3 | 17 / 2 | |
| 3.0.2 | 17 / 2 | |
| 3.0.0 | 17 / 2 | |
| 2.3.19 | 10 / 1 | |
| 2.3.18 | 10 / 1 | |
| 2.3.17 | 10 / 1 | |
| 2.3.16 | 10 / 1 | |
| 2.3.15 | 10 / 1 | |
| 2.3.14 | 10 / 1 | |
| 2.3.13 | 10 / 1 | |
| 2.3.12 | 10 / 1 | |
| 2.3.11 | 10 / 1 | |
| 2.3.10 | 10 / 1 | |
| 2.3.9 | 10 / 1 | |
| 2.3.8 | 10 / 1 | |
| 2.3.7 | 10 / 1 | |
| 2.3.6 | 10 / 1 | |
| 2.3.5 | 10 / 1 | |
| 2.3.4 | 10 / 1 |
v3.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.