@hanzogui/button
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/get-button-sized | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/spacer | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/stacks | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/helpers | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/font-size | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/web | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/text | AI (phantom-deps): Same-org sibling dep; component library re-export pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal UI component package; missing description is consistent across the @hanzogui org. | ai | |
| phantom-deps | phantom-dep:@hanzogui/core | AI (phantom-deps): Same-org dependency; likely used transitively or in build config, not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/config-default | AI (phantom-deps): Same-org dependency; likely used in build tooling, stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org component library; missing metadata is typical for internal monorepo packages, not spam/malware. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 10 / 3 | |
| 3.0.3 | 10 / 3 | |
| 3.0.2 | 9 / 3 | |
| 3.0.1 | 9 / 3 | |
| 3.0.0 | 9 / 3 | |
| 2.0.8 | 9 / 3 | |
| 2.0.7 | 9 / 3 | |
| 2.0.6 | 9 / 3 | |
| 2.0.5 | 9 / 3 | |
| 2.0.4 | 9 / 3 | |
| 2.0.0 | 9 / 3 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.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.