es6-module-jstransform
jstranform for es6 modules syntax
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:esprima-fb | AI (dependencies): esprima-fb is a Facebook fork of esprima used as the expected parser for jstransform-based tooling; its use here is intentional and appropriate for this package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Package is over 12 years old and predates Sigstore provenance tooling; absence of attestation is expected and not a security concern for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 2 / 3 | |
| 0.1.3 | 2 / 3 | |
| 0.1.2 | 2 / 3 | |
| 0.1.1 | 2 / 3 | |
| 0.1.0 | 2 / 3 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.