ts-node
TypeScript execution environment and REPL for node.js, with source map support
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): ts-node is a well-established package; missing gitHead reflects a publish environment change, not a supply chain compromise. No other behavioral indicators present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): ts-node v10.9.1 is a known legitimate patch release by the established maintainer cspotcode. Dormancy metric does not reflect actual account takeover risk for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): ts-node is a CJS module loader/interceptor; dynamic require() with variable arguments is core to its functionality, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): ts-node is a well-established package from a trusted publisher; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 10.9.2 | 13 / 31 | |
| 10.9.1 | 13 / 31 | |
| 10.9.0 | 13 / 31 | |
| 10.8.2 | 13 / 30 | |
| 10.8.1 | 13 / 30 | |
| 10.8.0 | 13 / 30 | |
| 10.7.0 | 13 / 32 | |
| 10.6.0 | 13 / 32 | |
| 10.5.0 | 13 / 32 | |
| 10.4.0 | 12 / 32 | |
| 10.3.1 | 12 / 32 | |
| 10.3.0 | 12 / 32 | |
| 10.2.1 | 12 / 30 | |
| 10.2.0 | 12 / 30 | |
| 10.1.0 | 10 / 31 | |
| 10.0.0 | 10 / 30 | |
| 9.1.1 | 6 / 26 | |
| 9.1.0 | 6 / 26 | |
| 9.0.0 | 5 / 25 |
v10.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blakeembrey) than the most recent previously approved version (cspotcode) on 2023-12-08, but blakeembrey is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cspotcode.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.