@hanzogui/vite-plugin
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/react-native-web-lite | AI (phantom-deps): Same-org workspace dep; platform shim pattern. | ai | |
| phantom-deps | phantom-dep:outdent | AI (phantom-deps): Build-time or config-level usage; stable for this vite-plugin package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Build-time or config-level usage; stable for this vite-plugin package. | ai | |
| phantom-deps | phantom-dep:esm-resolve | AI (phantom-deps): Build-time or config-level usage; stable for this vite-plugin package. | ai | |
| phantom-deps | phantom-dep:react-native-web | AI (phantom-deps): Platform shim dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@hanzogui/proxy-worm | AI (phantom-deps): Same-org workspace dep re-exported at runtime; stable. | ai | |
| phantom-deps | phantom-dep:@hanzogui/react-native-svg | AI (phantom-deps): Same-org workspace dep; platform shim pattern. | ai | |
| phantom-deps | phantom-dep:@hanzogui/fake-react-native | AI (phantom-deps): Same-org workspace dep; platform shim pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package with approved publisher track record; sparse metadata reflects style, not malice. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 0 / 0 | |
| 4.4.0 | 10 / 2 | |
| 4.3.1 | 10 / 2 | |
| 3.0.6 | 10 / 2 | |
| 3.0.5 | 10 / 2 | |
| 3.0.2 | 10 / 2 | |
| 3.0.1 | 10 / 2 | |
| 3.0.0 | 10 / 2 | |
| 2.0.5 | 10 / 2 | |
| 2.0.4 | 10 / 2 | |
| 2.0.3 | 10 / 2 | |
| 2.0.2 | 10 / 2 | |
| 2.0.0 | 10 / 2 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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. 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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.