@hanzogui/cli
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:joi | AI (typosquat): Scoped @hanzogui org CLI tool; Levenshtein match to 'joi' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@hanzogui/vite-plugin | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo workspace packages. | ai | |
| phantom-deps | phantom-dep:@hanzogui/create-theme | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo workspace packages. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): CLI build tool; esbuild is a known implicit runtime/binary dependency pattern. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): CLI invokes tsc/ts-morph; typescript used implicitly as a runtime tool. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Dev server CLI; express likely used via config/dynamic require pattern. | ai | |
| phantom-deps | phantom-dep:get-port | AI (phantom-deps): Dev server CLI; get-port used alongside express, consistent with config-driven usage. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): Node built-in polyfill; commonly referenced in config without direct import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 21 / 4 | |
| 4.3.1 | 21 / 4 | |
| 3.0.6 | 21 / 4 | |
| 2.0.1 | 21 / 4 | |
| 2.0.0 | 21 / 4 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
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.