← Home

@peerbit/stream

npm Repository Homepage
11
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

marcus.pousette

Keywords

peerbit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:it-all AI (phantom-deps): Test/config-only reference; not a real runtime phantom dep for this package. ai
phantom-deps phantom-dep:libp2p AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
phantom-deps phantom-dep:yallist AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@libp2p/tcp AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:uint8arrays AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@dao-xyz/borsh AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@libp2p/websockets AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@chainsafe/libp2p-noise AI (phantom-deps): Config-only reference; stable false positive for this package. ai
phantom-deps phantom-dep:@chainsafe/libp2p-yamux AI (phantom-deps): Config-only reference; stable false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
5.0.17 27 / 5
5.0.16 27 / 5
5.0.15 27 / 5
5.0.14 27 / 5
5.0.10 27 / 5
5.0.8 27 / 5
5.0.7 27 / 5
5.0.4 27 / 5
5.0.3 27 / 5
5.0.2 27 / 5
4.5.0 27 / 5

v5.0.17

1 finding
LOW No provenance attestation provenance

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

v5.0.16

1 finding
LOW No provenance attestation provenance

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

v5.0.15

1 finding
LOW No provenance attestation provenance

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

v5.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.