@agora-js/media
media module across @agora-js packages
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:AgoraRTC_N-media.js | AI (source-diff): Standard minified SDK bundle with copyright header; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:AgoraRTC_N-media.esm.mjs | AI (source-diff): ESM variant of the same minified SDK bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Package ships a pre-bundled artifact; declared deps may be bundled into the output rather than imported at runtime. Expected pattern for SDK packages. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): @agora-js/media is a scoped WebRTC SDK package from AgoraIO; the levenshtein match to 'redis' is a clear false positive with no plausible confusion vector. | ai | |
| phantom-deps | phantom-dep:@agora-js/report | AI (phantom-deps): Same-org scoped package; may be bundled or used indirectly. Expected for Agora's modular SDK architecture. | ai | |
| phantom-deps | phantom-dep:webrtc-adapter | AI (phantom-deps): webrtc-adapter is likely bundled into the output artifact; phantom-dep finding is expected for pre-bundled SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects Agora's legitimate multi-package SDK structure; thin README is a quality issue, not a security signal. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.24.6 | 6 / 0 | |
| 4.24.5 | 6 / 0 | |
| 4.24.4 | 5 / 0 | |
| 4.24.3 | 5 / 0 | |
| 4.24.2 | 5 / 0 | |
| 4.24.1 | 5 / 0 | |
| 4.24.0 | 5 / 0 | |
| 4.23.4 | 5 / 0 | |
| 4.23.3 | 5 / 0 | |
| 4.23.2 | 5 / 0 | |
| 4.23.1 | 5 / 0 | |
| 4.23.0 | 5 / 0 | |
| 4.22.2 | 5 / 0 | |
| 4.22.1 | 5 / 0 | |
| 4.22.0 | 5 / 0 | |
| 4.21.0 | 6 / 0 | |
| 4.20.2 | 6 / 0 | |
| 4.20.1 | 6 / 0 | |
| 4.20.0 | 6 / 0 | |
| 4.19.3 | 6 / 0 | |
| 4.19.2 | 6 / 0 | |
| 4.19.1 | 6 / 0 | |
| 4.19.0 | 6 / 0 |
v4.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.