← Home

@peerbit/test-utils

Test utils for Peerbit

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

marcus.pousette

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 67)

View all versions
Version Deps Published
3.1.11 17 / 2
3.1.10 17 / 2
3.1.9 17 / 2
3.1.8 17 / 2
3.1.7 17 / 2
3.1.6 17 / 2
3.1.5 17 / 2
3.1.4 17 / 2
3.1.3 17 / 2
3.1.2 17 / 2
3.1.1 17 / 2
3.1.0 17 / 2
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

v3.1.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.