@hanzogui/core
Note: most of this logic moved into @hanzogui/web
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/helpers | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@hanzogui/use-event | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/react-native-use-pressable | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI library @hanzogui/core; name collision with 'cors' is coincidental, not impersonation. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 6 / 9 | |
| 4.4.0 | 6 / 9 | |
| 4.3.1 | 6 / 9 | |
| 3.0.6 | 6 / 9 | |
| 3.0.5 | 6 / 9 | |
| 3.0.2 | 6 / 9 | |
| 3.0.1 | 6 / 9 | |
| 3.0.0 | 6 / 9 | |
| 2.0.5 | 6 / 9 | |
| 2.0.4 | 6 / 9 | |
| 2.0.3 | 6 / 9 | |
| 2.0.2 | 6 / 9 | |
| 2.0.1 | 6 / 9 | |
| 2.0.0 | 6 / 9 |
v4.3.1
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.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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
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.