@jimp/js-tiff
<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/tiff</h1> <p>Default Jimp tiff encoder/decoder.</p> </div>
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo scoped package; sparse README/description/keywords are normal for @jimp/* sub-packages. Inflated semver reflects coordinated monorepo versioning, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Part of the @jimp monorepo; sub-packages routinely omit standalone descriptions. Not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:@jimp/core | AI (phantom-deps): Same-org monorepo dependency; @jimp/core is used as a type/peer dependency, not necessarily directly imported in every file. | ai | |
| provenance | no-provenance | AI (provenance): Trusted publisher with long track record; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 3 / 11 | |
| 1.6.0 | 3 / 11 | |
| 1.5.0 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.0 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.5 | 3 / 11 | |
| 1.1.4 | 3 / 11 | |
| 1.1.3 | 3 / 11 | |
| 1.1.2 | 3 / 11 | |
| 1.1.1 | 3 / 11 | |
| 1.1.0 | 3 / 11 | |
| 1.0.5 | 3 / 11 | |
| 1.0.4 | 3 / 11 | |
| 1.0.3 | 3 / 11 | |
| 1.0.2 | 3 / 10 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.