@hanzogui/build
A small, opinionated build script for libraries that target both React Native and React 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @hanzogui/build; name reflects org+purpose, not an impersonation of uuid. | ai | |
| typosquat | typosquat.levenshtein:esbuild | AI (typosquat): Scoped package @hanzogui/build; name reflects org+purpose, not an impersonation of esbuild. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Build tool; execa referenced in config files is a normal pattern for CLI toolchains. | ai | |
| phantom-deps | phantom-dep:esbuild-register | AI (phantom-deps): Build tool; esbuild-register loaded by convention in config files. | ai | |
| phantom-deps | phantom-dep:baseline-browser-mapping | AI (phantom-deps): Referenced in config files; consistent with a bundler/build tool pattern. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Framework-scoped Babel preset; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): Type-only package; not directly imported by design. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 15 / 1 | |
| 4.4.0 | 15 / 1 | |
| 4.3.1 | 15 / 1 | |
| 3.0.6 | 15 / 1 | |
| 3.0.5 | 15 / 1 | |
| 3.0.2 | 15 / 1 | |
| 3.0.1 | 15 / 1 | |
| 3.0.0 | 15 / 1 | |
| 2.0.5 | 15 / 1 | |
| 2.0.4 | 15 / 1 | |
| 2.0.3 | 15 / 1 | |
| 2.0.2 | 15 / 1 | |
| 2.0.1 | 15 / 1 | |
| 2.0.0 | 15 / 1 |
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.