@hanzogui/menu
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/core | AI (phantom-deps): Same-org transitive dep; re-exported or used indirectly. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/helpers | AI (phantom-deps): Same-org transitive dep; re-exported or used indirectly. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/popover | AI (phantom-deps): Same-org transitive dep; re-exported or used indirectly. Stable for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 7 / 2 | |
| 3.0.0 | 7 / 2 | |
| 2.0.8 | 7 / 2 | |
| 2.0.7 | 7 / 2 | |
| 2.0.5 | 7 / 2 | |
| 2.0.0 | 7 / 2 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
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.