@hanzo/gui
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @hanzo/gui is a scoped UI library with no semantic resemblance to uuid; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Same rationale — scoped package name, no resemblance to the HTTP client 'got'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same rationale — no resemblance to the validation library 'joi'. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same rationale — no resemblance to the validation library 'yup'. | ai | |
| phantom-deps | phantom-dep:@hanzogui/focusable | AI (phantom-deps): Monorepo sub-package; may be re-exported transitively rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-token | AI (phantom-deps): Same — monorepo sub-package used via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-font-sized | AI (phantom-deps): Same — monorepo sub-package used via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-button-sized | AI (phantom-deps): Same — monorepo sub-package used via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/fake-react-native | AI (phantom-deps): Platform-specific binary package; phantom-dep heuristic is expected to misfire here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 63 / 4 | |
| 4.3.3 | 74 / 4 | |
| 2.0.7 | 20 / 4 | |
| 2.0.6 | 20 / 4 | |
| 2.0.5 | 18 / 4 | |
| 2.0.4 | 18 / 4 | |
| 2.0.3 | 18 / 4 | |
| 2.0.2 | 18 / 4 | |
| 2.0.1 | 18 / 4 |
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.