@jimp/plugin-hash
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): jimp underwent a major v1.x rewrite; dormancy reflects project hiatus, not account takeover. Trusted long-standing publisher with zero rejections. | ai | |
| phantom-deps | phantom-dep:@jimp/core | AI (phantom-deps): Same-org @jimp/* deps are part of the plugin architecture; indirect/transitive use is expected in this monorepo. | ai | |
| phantom-deps | phantom-dep:@jimp/js-bmp | AI (phantom-deps): Same-org @jimp/* deps used as peer/transitive dependencies in jimp plugin architecture. | ai | |
| phantom-deps | phantom-dep:@jimp/js-png | AI (phantom-deps): Same-org @jimp/* deps used as peer/transitive dependencies in jimp plugin architecture. | ai | |
| phantom-deps | phantom-dep:@jimp/js-jpeg | AI (phantom-deps): Same-org @jimp/* deps used as peer/transitive dependencies in jimp plugin architecture. | ai | |
| phantom-deps | phantom-dep:@jimp/js-tiff | AI (phantom-deps): Same-org @jimp/* deps used as peer/transitive dependencies in jimp plugin architecture. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 10 / 11 | |
| 1.6.0 | 10 / 11 | |
| 1.5.0 | 10 / 11 | |
| 1.4.0 | 10 / 11 | |
| 1.3.0 | 10 / 11 | |
| 1.2.0 | 10 / 11 | |
| 1.1.5 | 10 / 11 | |
| 1.1.4 | 10 / 11 | |
| 1.1.3 | 10 / 11 | |
| 1.1.2 | 10 / 11 | |
| 1.1.1 | 10 / 11 | |
| 1.1.0 | 10 / 11 | |
| 1.0.5 | 10 / 11 | |
| 1.0.4 | 10 / 11 | |
| 1.0.3 | 10 / 11 | |
| 1.0.2 | 10 / 11 |
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.5.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.