image-q
Image Quantization Library in **TypeScript** *(MIT Licensed)*
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish environment change for a monorepo package; same long-standing publisher. Not a security signal. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a TypeScript type declaration; listed as runtime dep is suboptimal but not a security concern. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 1 / 4 | |
| 3.0.8 | 1 / 4 | |
| 3.0.7 | 1 / 4 | |
| 3.0.6 | 1 / 4 | |
| 3.0.5 | 1 / 4 | |
| 3.0.4 | 1 / 4 | |
| 3.0.3 | 1 / 6 | |
| 3.0.2 | 1 / 6 | |
| 3.0.1 | 1 / 6 | |
| 3.0.0 | 1 / 6 | |
| 2.1.2 | 1 / 21 | |
| 2.1.1 | 1 / 21 | |
| 2.0.7 | 1 / 21 | |
| 2.0.6 | 1 / 19 | |
| 2.0.5 | 1 / 19 | |
| 2.0.4 | 0 / 20 | |
| 2.0.3 | 0 / 17 | |
| 2.0.1 | 0 / 17 | |
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 7 | |
| 1.0.1 | 0 / 6 | |
| 0.1.4 | 0 / 1 | |
| 0.1.3 | 0 / 1 | |
| 0.1.2 | 0 / 1 | |
| 0.1.1 | 0 / 1 | |
| 0.1.0 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.1 | 0 / 1 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: igor.bezkrovnyi.
v3.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: igor.bezkrovnyi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: igor.bezkrovnyi.
v3.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: igor.bezkrovnyi.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: igor.bezkrovnyi.