@volcengine/rtc
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:extension-rush/index.umd.js | AI (source-diff): UMD variant of the same SDK extension; same rationale as index.js. | ai | |
| source-diff | obfuscated-file:extension-rush/index.js | AI (source-diff): Minified SDK bundle consistent with existing extension pattern; not obfuscated malware. | ai | |
| source-diff | net-exec-file:extension-rush/index.js | AI (source-diff): WebRTC SDK legitimately combines network calls and dynamic code; matches established extension pattern. | ai | |
| source-diff | encoded-string-file:extension-ainr/index.umd.js | AI (source-diff): Minified UMD bundle; same pattern as other SDK files, no malicious content. | ai | |
| source-diff | encoded-string-file:extension-ainr/index.js | AI (source-diff): Minified SDK bundle; long strings are standard JS polyfill patterns, not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:index.esm.min.js | AI (source-diff): Minified WebRTC SDK bundle; long strings are standard minified JS, not encoded payloads. | ai | |
| source-diff | encoded-string-file:index.min.js | AI (source-diff): Minified WebRTC SDK bundle; long strings are standard minified JS, not encoded payloads. | ai | |
| source-diff | encoded-string-file:index.esm.nopolyfill.min.js | AI (source-diff): Minified WebRTC SDK bundle; long strings are standard minified JS, not encoded payloads. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.68.5 | 1 / 0 | |
| 4.68.4 | 1 / 0 | |
| 4.68.3 | 1 / 0 | |
| 4.67.17 | 1 / 0 | |
| 4.67.16 | 1 / 0 | |
| 4.66.38 | 1 / 0 | |
| 4.66.37 | 1 / 0 | |
| 4.46.19 | 1 / 0 | |
| 4.46.18 | 1 / 0 | |
| 4.45.8 | 1 / 0 | |
| 4.45.7 | 1 / 0 |
v4.68.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.68.4
4 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.68.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.67.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.38
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.37
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.45.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.