@mescius/wijmo.pdf
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:es2015-commonjs.js | AI (source-diff): Long strings are embedded font/binary data in a PDF library bundle; consistent across all versions of this package. | ai | |
| source-diff | encoded-string-file:es2015-esm.js | AI (source-diff): Same pattern — minified PDF library bundle with embedded binary data, not malicious encoding. | ai | |
| source-diff | encoded-string-file:es5-esm.js | AI (source-diff): Same pattern — minified PDF library bundle with embedded binary data, not malicious encoding. | ai | |
| source-diff | encoded-string-file:index.js | AI (source-diff): Same pattern — minified PDF library bundle with embedded binary data, not malicious encoding. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-publisher sibling package; stable false positive for the entire @mescius/wijmo.* ecosystem. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.20261.50 | 1 / 0 | |
| 5.20261.48 | 1 / 0 | |
| 5.20252.44 | 1 / 0 | |
| 5.20252.42 | 1 / 0 | |
| 5.20251.40 | 1 / 0 |
v5.20261.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20261.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20252.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20252.42
5 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 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.
v5.20251.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.