@sphinxxxx/color-conversion
Convert colors between RGBA/HSLA/Hex
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/color.js | AI (source-diff): The long encoded string is a documented compact encoding of CSS named colors (3-char hash + 4-char base64 RGB), not a malicious payload. Stable for this package. | ai | |
| source-diff | encoded-string-file:dist/color-conversion.js | AI (source-diff): The long encoded string is a compressed CSS color-name lookup table, a standard technique in color libraries. Not a malicious payload. | ai | |
| source-diff | encoded-string-file:dist/color-conversion.min.js | AI (source-diff): Same compressed color-name table in the minified build artifact. Benign and consistent with the package's documented purpose. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.2 | 0 / 12 | |
| 2.2.1 | 0 / 12 | |
| 2.2.0 | 0 / 12 | |
| 2.1.1 | 0 / 12 | |
| 2.1.0 | 0 / 12 | |
| 2.0.0 | 0 / 12 |
v2.2.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.