d3-scale-chromatic
Sequential, diverging and categorical color schemes.
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 | publisher-changed | AI (provenance): mbostock is the original D3 author reclaiming the package from a prior publisher; this is a legitimate transition, not a compromise. | ai | |
| source-diff | encoded-string-file:dist/d3-scale-chromatic.js | AI (source-diff): Long hex strings are color palette data (Viridis, Magma, etc.) encoded as compact hex RGB triplets — core functionality of this color scheme library, not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/d3-scale-chromatic.min.js | AI (source-diff): Same color palette hex strings in the minified bundle. Expected and legitimate for this package's purpose. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.0.0 | 2 / 4 | |
| 1.5.0 | 2 / 4 | |
| 1.4.0 | 2 / 4 | |
| 1.3.3 | 2 / 4 | |
| 1.3.2 | 2 / 4 | |
| 1.3.1 | 2 / 4 | |
| 1.3.0 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.1 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.2 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.0 | 1 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.1 | 0 / 5 |
v3.1.0
3 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-05. 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
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-23. This could indicate a legitimate maintainer transition or an account compromise.