@hanzogui/collapsible
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org component library; missing metadata is a style choice, not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across @hanzogui/* org packages; not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@hanzogui/stacks | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/web | AI (phantom-deps): Same-org sibling; likely re-exported via barrel, stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@hanzogui/helpers | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/animate-presence | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/use-controllable-state | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | 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/polyfill-dev | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/core | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for transitive/re-exported org packages. | ai | |
| phantom-deps | phantom-dep:@hanzogui/compose-refs | 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 / 2 | |
| 3.0.2 | 9 / 2 | |
| 3.0.1 | 9 / 2 | |
| 3.0.0 | 9 / 2 | |
| 2.0.8 | 9 / 2 | |
| 2.0.7 | 9 / 2 | |
| 2.0.5 | 9 / 2 | |
| 2.0.4 | 9 / 2 | |
| 2.0.0 | 9 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.