@mux/mux-player-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/-GRS5X4TZ.mjs | AI (source-diff): esbuild-minified bundle output; consistent with build scripts in package.json. Stable FP for this package. | ai | |
| source-diff | obfuscated-file:dist/-5WVTFKRM.mjs | AI (source-diff): esbuild-minified bundle output; consistent with build scripts in package.json. Stable FP for this package. | ai | |
| source-diff | obfuscated-file:dist/-JV5XE2MO.mjs | AI (source-diff): esbuild-minified bundle output; consistent with documented build pipeline for this package. | ai | |
| source-diff | obfuscated-file:dist/-QQATPRK2.mjs | AI (source-diff): esbuild --minify output; consistent with build scripts and prior versions. | ai | |
| source-diff | obfuscated-file:dist/-VMG67VUR.mjs | AI (source-diff): esbuild --minify output; consistent with build scripts and prior versions. | ai | |
| source-diff | obfuscated-file:dist/-W6F6BQLK.mjs | AI (source-diff): esbuild-minified bundle output; standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/-GVE4IPC5.mjs | AI (source-diff): esbuild --minify output (code-split chunk); stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/-CMETF44P.mjs | AI (source-diff): esbuild --minify output for code-split chunk; standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/-I7FKDHZE.mjs | AI (source-diff): esbuild --minify output (code-split chunk); standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/-7QSXIX4N.mjs | AI (source-diff): esbuild-minified bundle output; standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/-KWFP7TC7.mjs | AI (source-diff): esbuild-minified bundle output; consistent with build config and prior versions. | ai | |
| source-diff | obfuscated-file:dist/-6Q2IQRPZ.mjs | AI (source-diff): esbuild --minify output (code-split chunk from lazy build); stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/-ROK4AKYD.mjs | AI (source-diff): esbuild --minify output; standard build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/-SE2QKKFU.mjs | AI (source-diff): esbuild --minify output; consistent with build scripts and prior versions. | ai | |
| source-diff | obfuscated-file:dist/-WLQCDVLW.mjs | AI (source-diff): esbuild --minify output; standard bundled dist for this package. | ai | |
| source-diff | obfuscated-file:dist/-LTJRRAKL.mjs | AI (source-diff): esbuild-minified bundle output; consistent with build scripts in package.json. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is declared as a runtime dep and externalized in esbuild build scripts; phantom-dep is a false positive here. | ai | |
| source-diff | obfuscated-file:dist/-2SMMP33F.mjs | AI (source-diff): esbuild minified output from lazy-splitting; content is readable React player code, not obfuscation. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 3 / 10 | |
| 3.12.0 | 3 / 10 | |
| 3.11.8 | 3 / 10 | |
| 3.11.7 | 3 / 10 | |
| 3.11.6 | 3 / 10 | |
| 3.11.5 | 3 / 10 | |
| 3.11.4 | 3 / 10 | |
| 3.10.2 | 3 / 10 | |
| 3.10.1 | 3 / 10 | |
| 3.10.0 | 3 / 10 | |
| 3.9.2 | 3 / 10 | |
| 3.9.1 | 3 / 10 | |
| 3.9.0 | 3 / 10 | |
| 3.8.0 | 3 / 10 | |
| 3.7.0 | 3 / 10 | |
| 3.6.1 | 3 / 10 | |
| 3.6.0 | 3 / 10 | |
| 3.5.3 | 3 / 10 | |
| 3.5.2 | 3 / 10 | |
| 3.5.1 | 3 / 10 | |
| 3.5.0 | 3 / 10 | |
| 3.4.1 | 3 / 10 | |
| 3.4.0 | 3 / 10 |
v3.13.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.