@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 — the axios compromise (March 2026) relied on exactly this gap.
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 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/efa65ddd28d7fe431e2c56e1bf601be180dbc095/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/b37e26b8796f21cac5a1cb2b6ec52cb95e18e6e2/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/b839b5c47dfd924c447383346c46fa75e03d4269/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/acc87bf1819093c789343ec6df841c2bc851f3ca/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/30493cc8bcb9e843883bd79772d3ae8a904c9dee/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/voxgig/create-sdkgen/blob/fabe6f9eaa81c96c4fbcd14dbc8154449bcf693d/src/create-sdkgen.ts#L224 222 | const cwd = Path.resolve(folder, SDK_FOLDER) 223 | > 224 | const env = { 225 | ...process.env, 226 | PATH: `${Path.dirname(process.execPath)}${Path.delimiter}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.