@stacksjs/zig-dtsx
High-performance DTS emitter written in Zig
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@stacksjs/dtsx | AI (phantom-deps): Same-org declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Binaries are the expected Zig build output for this DTS emitter package; consistent with package purpose. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.9.26 | 1 / 0 | |
| 0.9.25 | 1 / 0 | |
| 0.9.24 | 1 / 0 | |
| 0.9.23 | 1 / 0 | |
| 0.9.22 | 1 / 0 | |
| 0.9.21 | 1 / 0 | |
| 0.9.20 | 1 / 0 | |
| 0.9.18 | 1 / 0 | |
| 0.9.17 | 1 / 0 | |
| 0.9.16 | 1 / 0 | |
| 0.9.14 | 1 / 0 | |
| 0.9.13 | 1 / 0 | |
| 0.9.12 | 1 / 0 | |
| 0.9.11 | 1 / 0 | |
| 0.9.10 | 1 / 0 |
v0.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
2 findingsPackage contains compiled binaries that could be backdoors: • zig-out/bin/zig-dtsx.exe • zig-out/bin/zig-dtsx
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
2 findingsPackage contains compiled binaries that could be backdoors: • zig-out/bin/zig-dtsx.exe • zig-out/bin/zig-dtsx
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
2 findingsPackage contains compiled binaries that could be backdoors: • zig-out/bin/zig-dtsx • zig-out/bin/zig-dtsx.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
2 findingsPackage contains compiled binaries that could be backdoors: • zig-out/bin/zig-dtsx • zig-out/bin/zig-dtsx.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
2 findingsPackage contains compiled binaries that could be backdoors: • zig-out/bin/zig-dtsx • zig-out/bin/zig-dtsx.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.