simple-peer MIT 25 versions

simple-peer

npm Repository Homepage

Simple one-to-one WebRTC video/voice and data channels

25

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mafintoshferosssubstackmaxogdenrationalcodingyocontra

Keywords

datadata channeldata channel streamdata channelsp2ppeerpeerpeer-to-peerstreamvideovoicewebrtcwebrtc stream

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:get-browser-rtc	AI (dependencies): get-browser-rtc is a legitimate, expected dependency for a WebRTC library; its use is appropriate and stable across all versions of simple-peer.	ai	2026/04/25

Versions (showing 25 of 25)

Version	Deps	Published
9.11.1	7 / 17	2022-02-17
9.11.0	7 / 15	2021-04-13
9.10.0	7 / 15	2021-03-18
9.9.4	7 / 15	2021-03-17
9.9.3	7 / 15	2020-11-11
9.9.2	7 / 15	2020-11-11
9.9.1	7 / 15	2020-11-11
9.9.0	7 / 15	2020-11-11
9.8.0	6 / 15	2020-10-28
9.7.2	5 / 15	2020-05-12
9.7.1	5 / 15	2020-05-10
9.7.0	5 / 15	2020-04-22
9.6.2	5 / 14	2019-11-12
9.6.1	5 / 14	2019-11-06
9.6.0	5 / 14	2019-09-18
9.5.0	5 / 14	2019-08-02
9.4.0	5 / 14	2019-06-26
9.3.1	5 / 14	2019-06-26
9.3.0	5 / 14	2019-03-24
9.2.1	5 / 14	2019-01-19
9.2.0	5 / 15	2018-12-13
9.1.2	5 / 14	2018-05-23
9.1.1	5 / 14	2018-04-25
9.1.0	5 / 14	2018-04-20
9.0.0	5 / 15	2018-02-21

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.4

1 finding

LOW No provenance attestation provenance

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

v9.9.3

1 finding

LOW No provenance attestation provenance

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

v9.9.2

1 finding

LOW No provenance attestation provenance

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

v9.9.1

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

v9.8.0

1 finding

LOW No provenance attestation provenance

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

v9.7.2

1 finding

LOW No provenance attestation provenance

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

v9.7.1

1 finding

LOW No provenance attestation provenance

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

v9.7.0

1 finding

LOW No provenance attestation provenance

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

v9.6.2

1 finding

LOW No provenance attestation provenance

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

v9.6.1

1 finding

LOW No provenance attestation provenance

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

v9.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: rationalcoding → feross (on 2019-09-18, known maintainer) provenance

This version was published by a different npm account (feross) than the most recent previously approved version (rationalcoding) on 2019-09-18, but feross is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: rationalcoding → feross (on 2019-08-02, known maintainer) provenance

This version was published by a different npm account (feross) than the most recent previously approved version (rationalcoding) on 2019-08-02, but feross is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.4.0

1 finding

LOW No provenance attestation provenance

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

v9.3.1

1 finding

LOW No provenance attestation provenance

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

v9.3.0

1 finding

LOW No provenance attestation provenance

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

v9.2.1

2 findings

MEDIUM Publisher changed: feross → rationalcoding (on 2019-01-19, unremoved on npm for 2739d) provenance

This version was published by a different npm account (rationalcoding) than the most recent previously approved version (feross) on 2019-01-19. It has since remained available on npm for 2739 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v9.2.0

2 findings

MEDIUM Publisher changed: feross → rationalcoding (on 2018-12-13, unremoved on npm for 2776d) provenance

This version was published by a different npm account (rationalcoding) than the most recent previously approved version (feross) on 2018-12-13. It has since remained available on npm for 2776 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v9.1.2

1 finding

LOW No provenance attestation provenance

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

v9.1.1

1 finding

LOW No provenance attestation provenance

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

v9.1.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.

v9.0.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.