@hanzogui/config
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @hanzogui font packages replacing prior font deps; consistent internal refactor pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo config package; sparse metadata is expected for workspace-scoped packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo config package; missing description is a style choice, not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/colors | AI (phantom-deps): Same-org monorepo dep; declared in package.json, likely re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@hanzogui/react-native-media-driver | AI (phantom-deps): Same-org monorepo dep; consistent with config bundle re-export pattern. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.3.0 | 13 / 1 | |
| 7.0.0 | 13 / 1 | |
| 4.4.0 | 13 / 1 | |
| 4.3.1 | 13 / 1 | |
| 3.0.6 | 13 / 1 | |
| 3.0.5 | 13 / 1 | |
| 3.0.2 | 13 / 1 | |
| 3.0.1 | 13 / 1 | |
| 3.0.0 | 13 / 1 | |
| 2.0.5 | 13 / 1 | |
| 2.0.4 | 13 / 1 | |
| 2.0.3 | 13 / 1 | |
| 2.0.2 | 13 / 1 | |
| 2.0.1 | 13 / 1 | |
| 2.0.0 | 13 / 1 |
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.