jscodeshift
A toolkit for JavaScript codemods
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:child-process-import | AI (semgrep): jscodeshift's Runner.js legitimately uses child_process to spawn worker processes — this is core to its architecture and stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): jscodeshift's Worker.js dynamically requires user-supplied transform modules by design — this is the fundamental mechanism of the tool, not a vulnerability. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 17.1.1 | 18 / 4 | |
| 17.1.0 | 18 / 4 | |
| 0.16.1 | 19 / 5 | |
| 0.16.0 | 20 / 5 | |
| 0.15.2 | 20 / 5 | |
| 0.15.1 | 20 / 5 | |
| 0.15.0 | 19 / 5 | |
| 0.14.0 | 19 / 5 | |
| 0.13.1 | 19 / 5 | |
| 0.13.0 | 19 / 5 | |
| 0.12.0 | 19 / 5 | |
| 0.11.0 | 19 / 5 | |
| 0.10.0 | 19 / 5 | |
| 0.9.0 | 19 / 5 | |
| 0.8.0 | 20 / 5 | |
| 0.7.1 | 18 / 5 | |
| 0.7.0 | 18 / 5 | |
| 0.6.4 | 18 / 5 | |
| 0.6.3 | 18 / 5 | |
| 0.6.2 | 18 / 5 | |
| 0.6.1 | 18 / 5 | |
| 0.6.0 | 14 / 5 | |
| 0.5.1 | 15 / 5 | |
| 0.5.0 | 15 / 5 | |
| 0.4.1 | 15 / 5 | |
| 0.4.0 | 15 / 5 | |
| 0.3.32 | 16 / 5 | |
| 0.3.31 | 16 / 5 | |
| 0.3.30 | 17 / 5 | |
| 0.3.29 | 16 / 5 | |
| 0.3.28 | 16 / 4 | |
| 0.3.27 | 16 / 4 | |
| 0.3.26 | 16 / 2 | |
| 0.3.25 | 14 / 2 | |
| 0.3.24 | 14 / 2 | |
| 0.3.23 | 14 / 2 | |
| 0.3.22 | 14 / 2 | |
| 0.3.21 | 14 / 2 | |
| 0.3.20 | 11 / 4 | |
| 0.3.19 | 10 / 3 | |
| 0.3.18 | 10 / 3 | |
| 0.3.17 | 10 / 3 | |
| 0.3.16 | 10 / 3 | |
| 0.3.15 | 9 / 4 | |
| 0.3.14 | 9 / 4 | |
| 0.3.13 | 9 / 4 | |
| 0.3.12 | 9 / 4 | |
| 0.3.11 | 9 / 4 | |
| 0.3.10 | 9 / 4 | |
| 0.3.9 | 9 / 4 | |
| 0.3.8 | 9 / 4 |
v17.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.