@hanzogui/label
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 | no-provenance | AI (provenance): No provenance across this package family; not a per-version risk signal. | ai | |
| provenance | missing-githead | AI (provenance): Consistent monorepo publish pattern; missing gitHead likely reflects a build environment change, not tampering. | ai | |
| phantom-deps | phantom-dep:@hanzogui/constants | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/focusable | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/compose-refs | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/create-context | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/web | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-button-sized | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-font-sized | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/text | AI (phantom-deps): Monorepo UI component; same-org deps re-exported rather than directly imported. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @hanzogui component library style; not an indicator of malice here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped UI component library; sparse metadata is consistent across the @hanzogui package family. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 7.3.0 | 8 / 3 | |
| 7.0.0 | 8 / 3 | |
| 3.0.2 | 8 / 3 | |
| 3.0.1 | 8 / 3 | |
| 3.0.0 | 8 / 3 | |
| 2.0.8 | 8 / 3 | |
| 2.0.7 | 8 / 3 | |
| 2.0.5 | 8 / 3 | |
| 2.0.4 | 8 / 3 | |
| 2.0.0 | 8 / 3 |
v7.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zeekay.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zeekay.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.