@vc-shell/config-generator
Generate Vite configurations
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:vite-plugin-circular-dependency | AI (dependencies): Legitimate Vite plugin for circular dependency detection; no malware indicators, stable use in this config-generator package. | ai | |
| dependencies | unvetted-dep:vite-plugin-mkcert | AI (dependencies): vite-plugin-mkcert is a legitimate, widely-used Vite plugin; stable false positive for this config-generator package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 505 versions; lack of provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): vue is a legitimate declared runtime dependency for a Vite config generator; phantom-dep is a false positive here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 8 / 5 | |
| 2.0.5 | 8 / 5 | |
| 2.0.4 | 8 / 5 | |
| 2.0.3 | 8 / 5 | |
| 2.0.2 | 8 / 5 | |
| 2.0.1 | 8 / 5 | |
| 2.0.0 | 8 / 5 | |
| 1.2.3 | 5 / 5 | |
| 1.2.2 | 5 / 5 | |
| 1.2.1 | 5 / 5 | |
| 1.2.0 | 5 / 5 |
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andrew.kubyshkin) than the most recent previously approved version (virto) on 2026-05-25, but andrew.kubyshkin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.