@cdc/dashboard
React component for combining multiple visualizations into a single dashboard
2
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
mpallanschadoecooms13
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/cdcdashboard.js | AI (source-diff): Encoded strings are D3 color scale hex sequences (viridis, magma, plasma, etc.) — standard in data viz bundles, not malicious payloads. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Declared as a runtime dep in package.json; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:use-debounce | AI (phantom-deps): Declared as a runtime dep in package.json; phantom-dep heuristic fires incorrectly for this package. | ai |
v4.26.5
2 findings
HIGH
Long encoded string in modified file: dist/cdcdashboard.js
source-diff
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.