@git.zone/tsrun
run typescript programs efficiently
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Process runner intentionally forwards parent env to child processes; this is expected behavior for tsrun. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 3 / 3 | |
| 2.0.3 | 3 / 3 | |
| 2.0.2 | 3 / 3 | |
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 |
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
3 findingsSpreading entire process.env into an object — may capture all secrets 100 | const spawnOptions = { 101 | cwd: options?.cwd || process.cwd(), > 102 | env: { ...process.env, ...options?.env }, 103 | stdio: options?.stdio || 'pipe', 104 | shell: false,
Spreading entire process.env into an object — may capture all secrets 184 | const spawnOptions = { 185 | cwd: options?.cwd || process.cwd(), > 186 | env: { ...process.env, ...options?.env }, 187 | stdio: options?.stdio || 'pipe', 188 | shell: false,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.