@hanzogui/popper
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/use-controllable-state | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/core | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/stacks | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/floating | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/constants | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/get-token | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/compose-refs | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@hanzogui/start-transition | AI (phantom-deps): Monorepo re-export pattern; same org scope, stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org UI component library; sparse metadata is consistent across the @hanzogui scope, not a spam/malware indicator. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 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 |
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. 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. 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.