@redsift/dashboard
Dashboard component library as part of Red Sift's Design System. This package provides dashboard-related components and decorators to make charts and datagrid filterable using crossfilter2.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package from a known monorepo; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:d3-selection | AI (phantom-deps): d3 sub-modules declared as deps and used via config/types; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-transition | AI (phantom-deps): d3 sub-modules declared as deps and used via config/types; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-shape | AI (phantom-deps): d3 sub-modules declared as deps and used via config/types; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Emotion packages declared as deps; referenced in config files; stable false positive. | ai | |
| phantom-deps | phantom-dep:d3-svg-annotation | AI (phantom-deps): Declared dep, referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Emotion packages declared as deps; referenced in config files; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 12.5.4 | 11 / 50 | |
| 12.5.3 | 11 / 50 | |
| 12.5.2 | 11 / 50 | |
| 12.5.1 | 11 / 50 | |
| 12.5.0 | 11 / 50 | |
| 12.4.0 | 11 / 50 | |
| 12.3.0 | 11 / 51 | |
| 11.9.4 | 11 / 52 |
v12.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.