@mui/x-internal-exceljs-fork
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/exceljs.bare.js | AI (source-diff): DH modp primes in browserified bundle; standard crypto constants, not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/exceljs.bare.min.js | AI (source-diff): Minified version of the same browserified bundle with DH primes. | ai | |
| source-diff | encoded-string-file:dist/exceljs.js | AI (source-diff): DH modp primes in browserified bundle; standard crypto constants. | ai | |
| source-diff | encoded-string-file:dist/exceljs.min.js | AI (source-diff): Minified version of the same browserified bundle with DH primes. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for OOXML encryption salt handling in exceljs encryptor — legitimate cryptographic use, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node as a runtime dep is a known exceljs pattern; framework-scoped type package, not a real phantom dep concern. | ai |
v5.0.0
6 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cherniavskii) than the most recent previously approved version (arminmeh) on 2026-06-02, but cherniavskii 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.
v4.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.