← Home

jimp-compact

npm Repository Homepage

Compact version of Jimp

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pi0nuxt.bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/jimp.cjs AI (source-diff): dist/jimp.cjs is a webpack/ncc bundle of jimp; long lines are standard bundler output, not obfuscation. Stable for this package. ai
source-diff net-exec-file:dist/jimp.cjs AI (source-diff): jimp uses HTTP for remote image loading and Babel helpers trigger code-exec heuristics. Expected bundled behavior, not malware. ai
provenance publisher-changed AI (provenance): nuxt.bot → pi0 is a known transition within the unjs/Nuxt org; pi0 (Pooya Parsa) is the primary maintainer. ai
maintainer-change maintainer-added AI (maintainer-change): nuxt.bot is the Nuxt org bot account; adding it alongside pi0 is standard unjs org practice. ai

Versions (showing 21 of 21)

Show 1 prerelease
Version Deps Published
0.16.2 0 / 7
0.16.1 0 / 3
0.12.1 0 / 3
0.12.0 0 / 3
0.10.3 0 / 3
0.10.1 0 / 3
0.9.8 0 / 3
0.9.7 0 / 3
0.9.6 0 / 3
0.9.3 0 / 3
0.9.1 0 / 3
0.9.0 0 / 3
0.8.5 0 / 3
0.8.4 0 / 3
0.8.3 0 / 3
0.8.2 0 / 3
0.8.1 0 / 3
0.8.0 0 / 3
0.7.0 0 / 3
0.6.8 0 / 3
0.6.4 0 / 3

v0.16.2

4 findings
HIGH Publisher changed: nuxt.bot → pi0 (on 2021-09-20) provenance

This version was published by a different npm account than previous versions on 2021-09-20. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/jimp.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/jimp.cjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.8

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.