mp4box
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/log-fujxCbB6.d.cts | AI (source-diff): Bundled TypeScript declaration file; long lines from type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/log-fujxCbB6.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines from type unions, not obfuscation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 0 / 19 | |
| 2.2.0 | 0 / 19 | |
| 2.1.2 | 0 / 19 | |
| 2.1.1 | 0 / 19 | |
| 2.1.0 | 0 / 19 | |
| 2.0.0 | 0 / 19 |
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.