@libp2p/webrtc
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@libp2p/noise | AI (dependencies): @libp2p/noise is a core libp2p ecosystem package; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): achingbrain is the primary js-libp2p maintainer (1270 approved, 0 rejected, 2096 days history). Change from service account to maintainer account is a normal operational transition, not a takeover. | ai | |
| dependencies | unvetted-dep:node-datachannel | AI (dependencies): node-datachannel is the standard native WebRTC data channel library for Node.js; its use is expected and appropriate for a WebRTC transport package. | ai | |
| dependencies | unvetted-dep:it-protobuf-stream | AI (dependencies): it-protobuf-stream is a libp2p ecosystem utility; its use is expected in libp2p transport packages for protobuf-based signaling. | ai | |
| dependencies | unvetted-dep:react-native-webrtc | AI (dependencies): react-native-webrtc is used for React Native platform support, explicitly mapped in package.json's react-native field. Appropriate for a cross-platform WebRTC transport. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 6.0.24 | 33 / 11 | |
| 6.0.23 | 33 / 11 | |
| 6.0.22 | 33 / 11 | |
| 6.0.21 | 33 / 11 | |
| 6.0.20 | 33 / 11 | |
| 6.0.19 | 33 / 11 | |
| 6.0.18 | 34 / 11 | |
| 6.0.16 | 33 / 11 | |
| 6.0.15 | 33 / 11 | |
| 6.0.14 | 33 / 11 | |
| 6.0.13 | 33 / 11 | |
| 6.0.12 | 33 / 11 | |
| 6.0.11 | 33 / 11 | |
| 6.0.10 | 33 / 11 | |
| 6.0.9 | 33 / 11 | |
| 6.0.8 | 33 / 11 | |
| 6.0.7 | 33 / 11 | |
| 6.0.6 | 33 / 11 | |
| 6.0.5 | 33 / 11 | |
| 6.0.4 | 33 / 11 | |
| 6.0.3 | 33 / 11 | |
| 6.0.2 | 33 / 11 | |
| 6.0.1 | 33 / 11 | |
| 6.0.0 | 33 / 11 |
v6.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.14
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.13
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.11
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.