@hanzogui/native
Native setup modules for Hanzo GUI - portals, gesture handler, worklets, and more
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Provenance gap only; no code-level risk. Package has clean history and no other risk signals. | ai | |
| provenance | no-provenance | AI (provenance): Informational hygiene finding; not a security disqualifier for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.3.0 | 1 / 10 | |
| 7.0.0 | 0 / 10 | |
| 4.4.0 | 0 / 10 | |
| 4.3.1 | 0 / 10 | |
| 3.0.6 | 0 / 10 | |
| 3.0.5 | 0 / 10 | |
| 3.0.2 | 0 / 10 | |
| 3.0.1 | 0 / 10 | |
| 3.0.0 | 0 / 10 | |
| 2.0.5 | 0 / 10 | |
| 2.0.4 | 0 / 10 | |
| 2.0.3 | 0 / 10 | |
| 2.0.2 | 0 / 10 | |
| 2.0.1 | 0 / 10 | |
| 2.0.0 | 0 / 10 |
v7.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zeekay.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.