@voxgig/apidef
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 — 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:dynamic-require | AI (semgrep): Dynamic require in resolver.ts is a documented custom element loader resolving user-configured paths; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:diff | AI (phantom-deps): diff is declared in dependencies and used in the package; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): pino is a declared runtime logging dependency; likely used indirectly via config or transitive logging setup. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a declared runtime dependency for log formatting; phantom-dep heuristic false positive. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 4 / 2 | |
| 6.1.1 | 4 / 2 | |
| 6.0.0 | 4 / 2 | |
| 5.11.0 | 4 / 2 | |
| 5.10.0 | 4 / 2 | |
| 5.9.0 | 4 / 2 | |
| 5.8.2 | 4 / 2 | |
| 5.8.1 | 4 / 2 | |
| 5.7.0 | 4 / 2 | |
| 5.6.0 | 10 / 2 | |
| 5.5.0 | 10 / 2 | |
| 5.4.0 | 10 / 2 | |
| 5.3.0 | 10 / 2 | |
| 5.2.1 | 10 / 2 | |
| 5.1.1 | 10 / 2 | |
| 5.0.0 | 12 / 4 | |
| 4.1.0 | 12 / 4 | |
| 4.0.0 | 12 / 4 | |
| 3.9.1 | 11 / 5 | |
| 3.9.0 | 11 / 5 | |
| 3.8.0 | 11 / 5 | |
| 3.7.0 | 11 / 5 | |
| 3.6.0 | 11 / 5 | |
| 3.5.0 | 11 / 5 | |
| 3.4.0 | 11 / 5 | |
| 3.3.1 | 11 / 5 | |
| 3.1.1 | 11 / 5 | |
| 3.1.0 | 11 / 5 | |
| 3.0.2 | 11 / 5 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.