jimp
An image processing library written entirely in JavaScript.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-bitmap | AI (dependencies): node-bitmap is a legitimate BMP format dependency for this pure-JS image library; stable use across jimp's long history with no malicious signals. | ai | |
| source-diff | net-exec-file:browser/lib/jimp.js | AI (source-diff): Network calls (image loading) and dynamic patterns in the webpack bundle are legitimate for an image processing library's browser build, not dropper behavior. | ai | |
| source-diff | obfuscated-file:browser/lib/jimp.js | AI (source-diff): browser/lib/jimp.js is jimp's intentional webpack browser bundle, declared in package.json 'browser' field. Minification is expected for this build artifact. | ai | |
| phantom-deps | phantom-dep:regenerator-runtime | AI (phantom-deps): regenerator-runtime is a known implicit Babel async runtime dependency; not directly imported but legitimately required at runtime. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): request is a well-known, widely-used HTTP client library. Its use in jimp for URL-based image loading is expected and legitimate, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): jimp is a 4240-day-old package predating Sigstore provenance; absence of attestation is expected and not a security concern for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The flagged IP (127.0.0.1) is a localhost address in a console.log within a dev/demo server.js file. No network exfiltration; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/browser/index.js | AI (source-diff): dist/browser/index.js is a legitimate rollup+terser browser bundle for the jimp image library. Minified long lines are expected build output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/browser/index.js | AI (source-diff): Network and code execution patterns in jimp's browser bundle are expected for an image processing library that fetches and processes images in browser environments. | ai | |
| source-diff | obfuscated-file:browser.js | AI (source-diff): browser.js is a legitimate Rollup browser bundle for jimp, produced by the documented build:browser script. Minification is expected and not malicious. | ai | |
| source-diff | net-exec-file:browser.js | AI (source-diff): Network and dynamic code patterns in browser.js are from bundled polyfills (Buffer, ieee754) in a browser image-processing bundle, not dropper/loader behavior. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely due to the addition of the browser.js bundle and its source map, which are documented build artifacts for browser compatibility. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval-usage fires on minified ieee754 library code in the browser bundle — a stable false positive for this package's browser build artifact. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): hex-decode fires on minified ieee754 library code in the browser bundle — a stable false positive for this package's browser build artifact. | ai | |
| phantom-deps | phantom-dep:@rspack/cli | AI (phantom-deps): @rspack/cli is a legitimate build tool accidentally listed in dependencies instead of devDependencies; not imported at runtime and not a security risk. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects monorepo refactor: jimp 1.x is a thin orchestrator delegating to @jimp/* scoped packages. Not a stub/redirect concern. | ai |
Versions (showing 100 of 143)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 27 / 21 | |
| 1.6.0 | 27 / 21 | |
| 1.4.0 | 27 / 21 | |
| 1.3.0 | 27 / 21 | |
| 1.2.0 | 27 / 21 | |
| 1.1.5 | 27 / 21 | |
| 1.1.4 | 27 / 21 | |
| 1.1.3 | 27 / 21 | |
| 1.1.2 | 27 / 21 | |
| 1.1.1 | 27 / 21 | |
| 1.1.0 | 27 / 21 | |
| 1.0.5 | 26 / 21 | |
| 1.0.4 | 26 / 20 | |
| 1.0.3 | 26 / 20 | |
| 1.0.2 | 27 / 20 | |
| 0.22.12 | 4 / 6 | |
| 0.22.11 | 4 / 6 | |
| 0.22.10 | 4 / 6 | |
| 0.22.9 | 4 / 6 | |
| 0.22.8 | 4 / 6 | |
| 0.22.7 | 4 / 6 | |
| 0.22.6 | 4 / 6 | |
| 0.22.5 | 4 / 6 | |
| 0.22.4 | 4 / 6 | |
| 0.22.3 | 4 / 6 | |
| 0.22.2 | 4 / 5 | |
| 0.22.1 | 4 / 5 | |
| 0.22.0 | 4 / 5 | |
| 0.21.3 | 4 / 5 | |
| 0.21.2 | 4 / 5 | |
| 0.21.1 | 4 / 5 | |
| 0.21.0 | 4 / 5 | |
| 0.20.2 | 5 / 16 | |
| 0.20.1 | 5 / 16 | |
| 0.20.0 | 5 / 16 | |
| 0.19.0 | 5 / 16 | |
| 0.18.0 | 5 / 16 | |
| 0.17.10 | 5 / 16 | |
| 0.17.9 | 5 / 32 | |
| 0.17.8 | 5 / 32 | |
| 0.17.7 | 5 / 32 | |
| 0.17.6 | 5 / 32 | |
| 0.17.5 | 5 / 32 | |
| 0.17.4 | 5 / 32 | |
| 0.17.3 | 5 / 32 | |
| 0.17.2 | 5 / 32 | |
| 0.17.1 | 5 / 32 | |
| 0.17.0 | 5 / 32 | |
| 0.16.13 | 5 / 32 | |
| 0.16.12 | 5 / 32 | |
| 0.16.11 | 5 / 32 | |
| 0.16.10 | 5 / 32 | |
| 0.16.9 | 5 / 32 | |
| 0.16.8 | 5 / 32 | |
| 0.16.7 | 5 / 32 | |
| 0.16.6 | 5 / 32 | |
| 0.16.5 | 5 / 32 | |
| 0.16.4 | 5 / 33 | |
| 0.16.3 | 5 / 33 | |
| 0.16.2 | 5 / 35 | |
| 0.16.1 | 5 / 35 | |
| 0.16.0 | 5 / 35 | |
| 0.15.0 | 5 / 35 | |
| 0.14.0 | 5 / 35 | |
| 0.13.0 | 5 / 35 | |
| 0.12.1 | 5 / 35 | |
| 0.12.0 | 5 / 35 | |
| 0.11.0 | 5 / 35 | |
| 0.10.3 | 6 / 35 | |
| 0.10.2 | 6 / 35 | |
| 0.10.1 | 6 / 35 | |
| 0.10.0 | 6 / 35 | |
| 0.9.8 | 6 / 35 | |
| 0.9.7 | 6 / 35 | |
| 0.9.6 | 6 / 35 | |
| 0.9.5 | 6 / 36 | |
| 0.9.4 | 6 / 36 | |
| 0.9.3 | 6 / 36 | |
| 0.9.1 | 5 / 36 | |
| 0.9.0 | 5 / 36 | |
| 0.8.5 | 5 / 36 | |
| 0.8.4 | 5 / 7 | |
| 0.8.3 | 5 / 7 | |
| 0.8.2 | 5 / 7 | |
| 0.8.1 | 5 / 7 | |
| 0.8.0 | 5 / 7 | |
| 0.7.0 | 5 / 7 | |
| 0.6.8 | 5 / 7 | |
| 0.6.7 | 5 / 7 | |
| 0.6.6 | 5 / 7 | |
| 0.6.5 | 5 / 7 | |
| 0.6.4 | 5 / 2 | |
| 0.6.3 | 5 / 2 | |
| 0.6.2 | 5 / 2 | |
| 0.6.1 | 5 / 2 | |
| 0.6.0 | 5 / 2 | |
| 0.5.6 | 5 / 2 | |
| 0.5.5 | 5 / 2 | |
| 0.5.4 | 5 / 2 | |
| 0.5.3 | 5 / 2 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.10
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.