← Home

utif

npm Repository Homepage

Fast and advanced TIFF decoder

11
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

photopeascimonster

Keywords

tiffimageconversion

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:jpgjs AI (dependencies): jpgjs GitHub dep has been stable since at least v1.3.0; it's a known jpg.js fork used for JPEG-in-TIFF support in this well-established package. ai
npm-metadata url-dep:jpgjs AI (npm-metadata): Same GitHub URL dep — long-standing, stable pattern for this package; not a new or suspicious addition. ai
provenance publisher-changed AI (provenance): Scimonster is listed as a contributor in package.json; publisher change occurred in 2019 and is a legitimate maintainer transition. ai

Versions (showing 11 of 11)

Version Deps Published
3.1.0 1 / 0
3.0.0 1 / 0
2.0.1 1 / 0
2.0.0 2 / 0
1.3.0 2 / 0
1.2.1 2 / 0
1.2.0 2 / 0
1.1.2 2 / 0
1.1.1 2 / 0
1.1.0 2 / 0
1.0.0 1 / 0

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

2 findings
HIGH Publisher changed: alisowski → scimonster (on 2019-02-11) provenance

This version was published by a different npm account than previous versions on 2019-02-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: scimonster → alisowski (on 2018-09-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-01. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.0

1 finding
LOW No provenance attestation provenance

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