@voxgig/create-sdkgen
Create a Voxgig SDK Generator project
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env spread is used to pass augmented PATH to child process; standard subprocess spawn pattern, not exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified root module by resolved path; expected SDK generator plugin-loading pattern. | ai | |
| phantom-deps | phantom-dep:aontu | AI (phantom-deps): Listed as devDependency in package.json template; used indirectly via generated project config. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Likely used transitively or in generated project scripts, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:shape | AI (phantom-deps): Referenced in config files as noted; stable false positive for this package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.16.3 | 5 / 3 | |
| 0.16.2 | 5 / 3 | |
| 0.16.1 | 5 / 3 | |
| 0.16.0 | 5 / 3 | |
| 0.15.0 | 5 / 3 | |
| 0.14.0 | 5 / 3 | |
| 0.13.1 | 5 / 3 | |
| 0.13.0 | 5 / 3 | |
| 0.12.2 | 5 / 3 | |
| 0.12.1 | 5 / 3 | |
| 0.12.0 | 5 / 3 | |
| 0.11.0 | 5 / 3 | |
| 0.10.1 | 5 / 3 | |
| 0.9.1 | 5 / 3 | |
| 0.9.0 | 5 / 3 | |
| 0.8.0 | 5 / 3 | |
| 0.7.1 | 5 / 3 | |
| 0.7.0 | 5 / 3 | |
| 0.6.0 | 5 / 3 | |
| 0.5.1 | 5 / 3 | |
| 0.5.0 | 5 / 3 | |
| 0.4.0 | 5 / 5 | |
| 0.3.1 | 5 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.0 | 5 / 5 | |
| 0.1.2 | 5 / 5 | |
| 0.1.1 | 5 / 5 | |
| 0.1.0 | 5 / 5 | |
| 0.0.9 | 5 / 5 | |
| 0.0.8 | 5 / 5 | |
| 0.0.7 | 5 / 5 | |
| 0.0.6 | 5 / 5 | |
| 0.0.2 | 4 / 5 | |
| 0.0.1 | 2 / 5 |
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.