@jimp/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @jimp/core is the core module of the well-established Jimp image library, not a typosquat of cors. The name similarity is purely coincidental; this is a stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): The hex decode is standard bitmap pixel data processing (int → hex string → Buffer bytes), not obfuscation or payload hiding. Stable false positive for this image processing package. | ai |
Versions (showing 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 11 / 1 | |
| 0.3.8 | 10 / 1 | |
| 0.3.7 | 10 / 1 | |
| 0.3.6 | 10 / 1 |
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.