@hanzogui/checkbox-headless
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:@hanzogui/web | AI (phantom-deps): Monorepo component library; same-org deps may be consumed indirectly or via re-exports. | ai | |
| phantom-deps | phantom-dep:@hanzogui/label | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@hanzogui/helpers | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@hanzogui/constants | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@hanzogui/compose-refs | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@hanzogui/use-previous | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for this package structure. | ai | |
| phantom-deps | phantom-dep:@hanzogui/focusable | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on build-time or peer usage patterns common in UI component libraries. | ai | |
| phantom-deps | phantom-dep:@hanzogui/create-context | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/use-controllable-state | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 9 / 3 | |
| 3.0.2 | 9 / 3 | |
| 3.0.1 | 9 / 3 | |
| 3.0.0 | 9 / 3 | |
| 2.0.8 | 9 / 3 | |
| 2.0.7 | 9 / 3 | |
| 2.0.5 | 9 / 3 | |
| 2.0.4 | 9 / 3 | |
| 2.0.0 | 9 / 3 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.