@cdc/data-table
React standalone data table component
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chroma | AI (phantom-deps): Declared dep in monorepo component; phantom-dep heuristic false positive for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:chroma-js | AI (phantom-deps): Monorepo component; deps declared at package level but consumed via bundled build config, not direct imports. | ai | |
| phantom-deps | phantom-dep:papaparse | AI (phantom-deps): Same monorepo bundling pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:whatwg-fetch | AI (phantom-deps): Same monorepo bundling pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-react-parser | AI (phantom-deps): Same monorepo bundling pattern; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.26.5 | 7 / 5 | |
| 4.26.4 | 7 / 5 | |
| 4.26.3 | 7 / 5 | |
| 4.26.2 | 7 / 5 | |
| 4.26.1 | 8 / 5 | |
| 4.25.11 | 8 / 4 | |
| 4.25.10 | 8 / 5 |
v4.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.