@voxgig/sdkgen
Voxgig SDK Generator.
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:dynamic-require | AI (semgrep): Intentional plugin-loader pattern loading a user-configured root module; stable across versions of this SDK generator. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.3.14 | 0 / 5 | |
| 1.3.13 | 0 / 5 | |
| 1.3.12 | 0 / 5 | |
| 1.3.11 | 0 / 5 | |
| 1.3.10 | 0 / 5 | |
| 1.3.9 | 0 / 5 | |
| 1.3.8 | 0 / 5 | |
| 1.3.7 | 0 / 5 | |
| 1.3.6 | 0 / 5 | |
| 1.3.5 | 0 / 5 | |
| 1.3.4 | 0 / 5 | |
| 1.3.2 | 0 / 5 | |
| 1.3.1 | 0 / 5 | |
| 1.2.1 | 0 / 5 | |
| 1.2.0 | 0 / 5 | |
| 1.1.1 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 0.45.0 | 0 / 5 | |
| 0.44.0 | 0 / 5 | |
| 0.43.0 | 0 / 5 | |
| 0.42.3 | 0 / 5 | |
| 0.42.2 | 0 / 5 | |
| 0.42.1 | 0 / 5 | |
| 0.42.0 | 0 / 5 | |
| 0.41.1 | 0 / 5 | |
| 0.41.0 | 0 / 5 | |
| 0.40.2 | 0 / 5 | |
| 0.40.1 | 0 / 5 | |
| 0.39.1 | 0 / 5 | |
| 0.39.0 | 0 / 5 | |
| 0.38.1 | 0 / 5 | |
| 0.37.0 | 0 / 6 | |
| 0.36.0 | 0 / 6 | |
| 0.35.2 | 0 / 6 | |
| 0.35.1 | 0 / 6 | |
| 0.35.0 | 0 / 6 | |
| 0.34.11 | 0 / 6 | |
| 0.34.10 | 0 / 6 | |
| 0.34.8 | 0 / 6 | |
| 0.34.7 | 0 / 6 | |
| 0.34.6 | 0 / 6 | |
| 0.34.5 | 0 / 6 | |
| 0.34.4 | 0 / 6 | |
| 0.34.3 | 0 / 6 | |
| 0.34.2 | 0 / 6 | |
| 0.34.1 | 0 / 6 | |
| 0.34.0 | 0 / 6 | |
| 0.33.0 | 0 / 6 | |
| 0.32.3 | 0 / 6 | |
| 0.32.2 | 0 / 6 | |
| 0.32.1 | 0 / 6 | |
| 0.32.0 | 0 / 6 | |
| 0.31.0 | 0 / 6 | |
| 0.30.0 | 0 / 6 | |
| 0.28.0 | 0 / 6 | |
| 0.26.1 | 0 / 6 | |
| 0.25.0 | 0 / 6 | |
| 0.24.0 | 0 / 6 | |
| 0.23.0 | 0 / 6 | |
| 0.22.0 | 1 / 7 | |
| 0.21.0 | 1 / 7 | |
| 0.20.1 | 0 / 7 | |
| 0.19.0 | 0 / 7 | |
| 0.18.0 | 0 / 7 | |
| 0.17.0 | 0 / 7 | |
| 0.16.0 | 0 / 7 | |
| 0.15.0 | 0 / 7 | |
| 0.14.0 | 6 / 8 | |
| 0.13.0 | 3 / 8 | |
| 0.12.0 | 3 / 8 | |
| 0.11.1 | 3 / 8 | |
| 0.11.0 | 3 / 8 | |
| 0.10.2 | 3 / 8 | |
| 0.10.1 | 3 / 8 | |
| 0.10.0 | 3 / 8 | |
| 0.9.1 | 3 / 8 | |
| 0.9.0 | 3 / 8 | |
| 0.8.0 | 3 / 8 | |
| 0.7.0 | 3 / 8 | |
| 0.6.0 | 3 / 8 | |
| 0.5.0 | 3 / 8 | |
| 0.4.0 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.2.0 | 3 / 8 | |
| 0.1.1 | 3 / 8 | |
| 0.1.0 | 3 / 8 | |
| 0.0.8 | 3 / 8 | |
| 0.0.7 | 1 / 6 | |
| 0.0.6 | 1 / 6 | |
| 0.0.5 | 1 / 6 | |
| 0.0.4 | 1 / 6 | |
| 0.0.3 | 1 / 6 | |
| 0.0.2 | 1 / 6 | |
| 0.0.1 | 1 / 6 |
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.