mediasoup-client
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:npm-events-package | AI (dependencies): npm alias for the well-known 'events' package; not a novel or suspicious dependency. | ai | |
| phantom-deps | phantom-dep:@types/npm-events-package | AI (phantom-deps): Type alias; not directly imported at runtime, stable false positive. | ai | |
| dependencies | unvetted-dep:@types/npm-events-package | AI (dependencies): npm alias for '@types/events'; standard type definitions, no risk. | ai | |
| dependencies | unvetted-dep:events-alias | AI (dependencies): npm alias for the well-known 'events' package; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@types/events-alias | AI (dependencies): npm alias for @types/events; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): Type-only package used by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/events-alias | AI (phantom-deps): Type alias package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:supports-color | AI (phantom-deps): Referenced in config/build context; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.20.0 | 9 / 15 | |
| 3.19.0 | 9 / 15 | |
| 3.18.8 | 9 / 15 | |
| 3.18.5 | 9 / 16 | |
| 3.18.3 | 9 / 16 | |
| 3.17.1 | 9 / 16 | |
| 3.16.6 | 9 / 16 | |
| 3.16.2 | 9 / 16 | |
| 3.16.1 | 9 / 16 | |
| 3.16.0 | 9 / 16 | |
| 3.15.4 | 10 / 16 | |
| 3.15.3 | 10 / 16 | |
| 3.15.2 | 10 / 15 | |
| 3.15.1 | 10 / 15 | |
| 3.12.4 | 10 / 16 | |
| 3.12.2 | 10 / 18 | |
| 3.10.0 | 10 / 18 |
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.