@hanzogui/dev-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo dev-config package; missing metadata is expected for org-internal packages. | ai | |
| phantom-deps | phantom-dep:@hanzogui/shorthands | AI (phantom-deps): Same-org dependency; stable false positive for this monorepo config package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/animations-css | AI (phantom-deps): Same-org dependency; stable false positive for this monorepo config package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/themes | AI (phantom-deps): Same-org dependency declared for re-export/bundling; not directly imported but legitimately part of the monorepo. | ai | |
| phantom-deps | phantom-dep:@hanzogui/animations-motion | AI (phantom-deps): Same-org dependency; stable false positive for this monorepo config package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/animations-reanimated | AI (phantom-deps): Same-org dependency; stable false positive for this monorepo config package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/animations-moti | AI (phantom-deps): Same-org dependency; stable false positive for this monorepo config package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 14 / 2 | |
| 4.4.0 | 14 / 2 | |
| 4.3.1 | 14 / 2 | |
| 3.0.6 | 14 / 2 | |
| 3.0.5 | 14 / 2 | |
| 2.0.2 | 14 / 2 | |
| 2.0.1 | 14 / 2 | |
| 2.0.0 | 14 / 2 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
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. 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.