@hashintel/ds-components
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 | source-size-tripled | AI (source-diff): Size increase driven by PandaCSS token/buildinfo output; not injected payload. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are PandaCSS codegen artifacts (tokens, buildinfo); expected for this package's CSS tooling migration. | ai | |
| dependencies | unvetted-dep:canvas | AI (dependencies): canvas is a well-known server-side rendering package; its use in a React component library is expected and benign. | ai | |
| provenance | no-provenance | AI (provenance): Established hashintel org package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@hashintel/ds-helpers | AI (phantom-deps): Same-org sibling package; likely re-exported rather than directly imported, stable FP. | ai | |
| phantom-deps | phantom-dep:@ark-ui/react | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this UI library package. | ai | |
| phantom-deps | phantom-dep:canvas | AI (phantom-deps): canvas is used in browser test/Storybook context, not a direct runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:motion | AI (phantom-deps): motion is a UI animation dep likely used indirectly via component composition; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 7 / 35 | |
| 0.1.2 | 5 / 27 | |
| 0.1.1 | 5 / 27 | |
| 0.0.4 | 5 / 27 | |
| 0.0.3 | 5 / 27 | |
| 0.0.1 | 4 / 18 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.