@csstools/convert-colors
Convert colors between RGB, HEX, HSL, HWB, LAB, LCH, and more
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:index.mjs | AI (source-diff): Minified Rollup+Terser output with source maps shipped; standard bundled library pattern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): romainmenke is a known csstools org contributor with a strong track record (894 approved, 0 rejected). This is a legitimate org-level maintainer transition, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (romainmenke, alaguna) are csstools org members. Legitimate org-level transfer consistent with the publisher's track record. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package is a stable color conversion utility; dormancy reflects completion, not abandonment. Revival by a known csstools org member for build tooling updates is benign. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 0 / 5 | |
| 2.0.0 | 0 / 11 | |
| 1.4.0 | 0 / 8 | |
| 1.3.0 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.0 | 0 / 8 |
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.