@webex/internal-media-core
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/esm/index.js | AI (source-diff): Same minified bundle pattern as CJS output; not malicious encoding. | ai | |
| source-diff | encoded-string-file:dist/cjs/index.js | AI (source-diff): Long strings are minified bundle output (async library code visible in sample), not encoded payloads. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@webex/web-capabilities | AI (phantom-deps): Same org scope; likely loaded by convention across Webex packages. | ai | |
| provenance | no-provenance | AI (provenance): Cisco/Webex packages consistently publish without Sigstore provenance; stable pattern. | ai | |
| phantom-deps | phantom-dep:xstate | AI (phantom-deps): xstate declared dep used via config/type references; stable false positive. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared dep used transitively/in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ip-anonymize | AI (phantom-deps): ip-anonymize declared dep; phantom-dep heuristic misfires for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Cisco/Webex proprietary package; no public repo or keywords is expected for this type of package. | ai | |
| phantom-deps | phantom-dep:@webex/ts-sdp | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundled output. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs2 | AI (phantom-deps): Babel runtime-corejs2 loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime loaded by convention in transpiled packages; stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.26.0 | 12 / 69 | |
| 2.25.1 | 12 / 69 | |
| 2.25.0 | 12 / 69 | |
| 2.24.1 | 12 / 69 | |
| 2.24.0 | 12 / 69 | |
| 2.23.3 | 12 / 69 | |
| 2.23.1 | 12 / 69 | |
| 2.23.0 | 12 / 69 | |
| 2.22.0 | 12 / 69 | |
| 2.21.0 | 12 / 69 | |
| 2.20.2 | 12 / 69 | |
| 2.20.1 | 12 / 69 | |
| 2.20.0 | 12 / 69 | |
| 2.18.4 | 12 / 69 | |
| 2.18.3 | 12 / 69 | |
| 2.18.1 | 12 / 69 | |
| 2.17.0 | 12 / 69 | |
| 2.16.2 | 12 / 69 | |
| 2.16.1 | 12 / 69 | |
| 2.15.0 | 11 / 68 | |
| 2.14.9 | 11 / 68 |
v2.26.0
4 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.
This version was published by a different npm account (webex-jenkins) than the most recent previously approved version (arun3528) on 2026-05-27, but webex-jenkins 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.
v2.25.1
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.
v2.25.0
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.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.