@webex/web-client-media-engine
Web Client Media Engine is common web code for interacting with the multistream media server.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/cjs/index.js | AI (source-diff): Base64 is rollup-plugin-web-worker-loader inlining worker bundle; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/esm/index.js | AI (source-diff): Same rollup web-worker-loader pattern in ESM build; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@webex/ts-events | AI (dependencies): Same Webex org scope; sibling package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@webex/rtcstats | AI (dependencies): Same Webex org scope; sibling package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@webex/webrtc-core | AI (dependencies): Same Webex org scope; sibling package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@webex/json-multistream | AI (dependencies): Same Webex org scope; sibling package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@webex/web-media-effects | AI (dependencies): Same Webex org scope; sibling package, not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Webex org package; provenance absence is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): async is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@webex/web-media-effects | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@webex/web-capabilities | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.40.0 | 11 / 35 | |
| 3.39.12 | 11 / 35 | |
| 3.39.11 | 11 / 35 | |
| 3.39.6 | 11 / 34 | |
| 3.39.4 | 11 / 34 | |
| 3.38.2 | 11 / 34 | |
| 3.35.3 | 11 / 36 | |
| 3.35.2 | 11 / 36 | |
| 3.35.0 | 11 / 36 | |
| 3.34.1 | 11 / 35 | |
| 3.33.2 | 11 / 35 | |
| 3.33.0 | 11 / 35 | |
| 3.32.0 | 11 / 35 | |
| 3.31.6 | 11 / 35 | |
| 3.31.3 | 11 / 35 | |
| 3.31.1 | 11 / 35 | |
| 3.30.3 | 11 / 35 |
v3.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.11
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.