@thi.ng/pixel-dominant-colors
k-means based dominant color extraction from images/pixel buffers
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): Internal thi.ng/umbrella monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/pixel | AI (dependencies): Internal thi.ng/umbrella monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/k-means | AI (dependencies): Internal thi.ng/umbrella monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Internal thi.ng/umbrella monorepo dependency; stable pattern across all versions. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 2.0.47 | 4 / 3 | |
| 2.0.46 | 4 / 3 | |
| 2.0.45 | 4 / 3 | |
| 2.0.43 | 4 / 3 | |
| 2.0.42 | 4 / 3 | |
| 2.0.40 | 4 / 3 | |
| 2.0.39 | 4 / 3 | |
| 2.0.38 | 4 / 3 | |
| 2.0.37 | 4 / 3 | |
| 2.0.36 | 4 / 3 | |
| 2.0.35 | 4 / 3 | |
| 2.0.34 | 4 / 3 | |
| 2.0.33 | 4 / 3 | |
| 2.0.32 | 4 / 3 | |
| 2.0.31 | 4 / 3 | |
| 2.0.29 | 4 / 3 | |
| 2.0.28 | 4 / 3 | |
| 2.0.27 | 4 / 3 | |
| 2.0.26 | 4 / 3 | |
| 2.0.25 | 4 / 3 | |
| 2.0.24 | 4 / 3 | |
| 2.0.23 | 4 / 3 | |
| 2.0.22 | 4 / 3 | |
| 2.0.21 | 4 / 3 | |
| 2.0.20 | 4 / 3 | |
| 2.0.19 | 4 / 3 | |
| 2.0.18 | 4 / 3 | |
| 2.0.14 | 4 / 3 | |
| 2.0.13 | 4 / 3 | |
| 2.0.12 | 4 / 3 | |
| 2.0.11 | 4 / 3 | |
| 2.0.10 | 4 / 3 | |
| 2.0.9 | 4 / 3 | |
| 2.0.8 | 4 / 3 | |
| 2.0.7 | 4 / 3 | |
| 2.0.6 | 4 / 3 | |
| 2.0.5 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.2 | 4 / 3 | |
| 2.0.1 | 4 / 3 | |
| 2.0.0 | 4 / 3 |
v2.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.