@jimp/plugin-quantize MIT 12 versions

@jimp/plugin-quantize

npm Repository Homepage

<div align="center"> <img width="200" height="200" src="https://s3.amazonaws.com/pix.iemoji.com/images/emoji/apple/ios-11/256/crayon.png"> <h1>@jimp/plugin-quantize</h1> <p>Reduces the number of colors in an image.</p> </div>

12

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

alisowskioliver.moran

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Part of the jimp monorepo; missing description/keywords and inflated semver are expected for coordinated monorepo releases, not spam indicators.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): Monorepo sub-package; no standalone description is normal for @jimp/* scoped packages.	ai	2026/04/23

Versions (showing 12 of 12)

Version	Deps	Published
1.6.1	2 / 12	2026-04-07
1.6.0	2 / 12	2024-09-09
1.5.0	2 / 12	2024-09-07
1.4.0	2 / 12	2024-09-07
1.3.0	2 / 11	2024-09-04
1.2.0	2 / 11	2024-09-03
1.1.5	2 / 11	2024-09-02
1.1.4	2 / 11	2024-09-02
1.1.3	2 / 11	2024-09-02
1.1.2	2 / 11	2024-09-02
1.1.1	2 / 11	2024-09-02
1.1.0	2 / 11	2024-09-01

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.5

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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.