@vc-shell/api-client-generator
Tool for API clients generation
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large established @vc-shell monorepo; dormancy followed by a clean no-change patch bump is consistent with normal release cadence resumption. | ai | |
| dependencies | unvetted-dep:nswag | AI (dependencies): nswag is a well-known OpenAPI/NSwag toolchain; its use is expected and appropriate for an API client generator package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:nswag | AI (phantom-deps): nswag is a runtime dep used via CLI/config, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vite-plugin-dts | AI (phantom-deps): vite-plugin-dts is referenced in vite config, not directly imported; stable false positive for this build tool. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 6 / 3 | |
| 2.0.5 | 6 / 3 | |
| 2.0.4 | 6 / 3 | |
| 2.0.3 | 6 / 3 | |
| 2.0.2 | 6 / 3 | |
| 2.0.1 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.2.3 | 6 / 3 | |
| 1.2.2 | 6 / 3 | |
| 1.2.1 | 6 / 3 | |
| 1.2.0 | 6 / 3 |
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.