@thi.ng/imago
JSON & API-based declarative and extensible image processing trees/pipelines
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/date | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/pixel | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/file-io | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/blurhash | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/defmulti | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/object-utils | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/pixel-dither | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.6.16 | 13 / 5 | |
| 1.6.15 | 13 / 5 | |
| 1.6.14 | 13 / 5 | |
| 1.6.12 | 13 / 5 | |
| 1.6.11 | 13 / 5 | |
| 1.6.9 | 13 / 5 | |
| 1.6.8 | 13 / 5 | |
| 1.6.7 | 13 / 5 | |
| 1.6.6 | 13 / 5 | |
| 1.6.5 | 13 / 5 | |
| 1.6.4 | 13 / 5 | |
| 1.6.3 | 13 / 5 | |
| 1.6.2 | 13 / 5 | |
| 1.6.1 | 13 / 5 | |
| 1.6.0 | 13 / 5 | |
| 1.5.10 | 13 / 5 | |
| 1.5.9 | 13 / 5 | |
| 1.5.8 | 13 / 5 | |
| 1.5.7 | 13 / 5 | |
| 1.5.6 | 13 / 5 | |
| 1.5.5 | 13 / 5 | |
| 1.5.4 | 13 / 5 | |
| 1.5.3 | 13 / 5 | |
| 1.5.2 | 13 / 5 | |
| 1.5.1 | 13 / 5 | |
| 1.5.0 | 13 / 5 | |
| 1.4.15 | 13 / 5 | |
| 1.4.14 | 13 / 5 | |
| 1.4.13 | 13 / 5 | |
| 1.4.9 | 13 / 5 | |
| 1.4.8 | 13 / 5 | |
| 1.4.7 | 13 / 5 | |
| 1.4.6 | 13 / 5 | |
| 1.4.5 | 13 / 5 | |
| 1.4.4 | 13 / 5 | |
| 1.4.2 | 13 / 5 | |
| 1.4.1 | 13 / 5 | |
| 1.4.0 | 13 / 5 | |
| 1.3.0 | 13 / 5 | |
| 1.2.4 | 13 / 5 | |
| 1.2.3 | 13 / 5 | |
| 1.2.2 | 13 / 5 | |
| 1.2.1 | 13 / 5 | |
| 1.2.0 | 13 / 5 | |
| 1.1.7 | 13 / 5 | |
| 1.1.6 | 13 / 5 | |
| 1.1.5 | 13 / 5 | |
| 1.1.4 | 13 / 5 | |
| 1.1.3 | 13 / 5 | |
| 1.1.2 | 13 / 5 | |
| 1.1.1 | 13 / 5 |
v1.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
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.