jstransform
A simple AST visitor-based JS transformer
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Historical spam flag on co-contributor; current publisher zpao has strong track record. Package metadata and repository are legitimate. | ai | |
| dependencies | unvetted-dep:esprima-fb | AI (dependencies): esprima-fb is a Facebook fork with stable version constraint; appropriate for this transformer and stable across 29 versions. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4570 days old; Sigstore provenance predates the package. Publisher is a known Facebook engineer with clean track record. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in test files is used to verify transformer output; legitimate for compiler/transformer test suites. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in test files verifies code generation; standard pattern for transformer testing. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 5 / 2 | |
| 7.0.0 | 3 / 1 | |
| 6.2.0 | 3 / 1 | |
| 6.0.0 | 3 / 1 | |
| 3.0.0 | 3 / 0 | |
| 2.0.3 | 3 / 0 | |
| 2.0.2 | 3 / 0 |
v7.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.
v6.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.
v6.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.
v3.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.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.