babel-generator
Turns an AST into code.
28
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
existentialismthejameskylesebmckdanezhzoologanfsmyth
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | — | sean | |
| maintainer-change | maintainer-added | AI (maintainer-change): hzoo, jmm, loganfsmyth are established Babel core team members. | ai | |
| bogus-package | bogus-package | AI (bogus-package): babel-generator is a legitimate core Babel package by the original Babel author. Sparse metadata is an artifact of early Babel v6 releases, not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): babel-generator is a legacy Babel 6 package published years before npm provenance attestation existed; absence of provenance is expected and not a risk signal for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 6.3.13 | 9 / 2 | |
| 6.3.1 | 9 / 2 | |
| 6.2.4 | 9 / 2 | |
| 6.2.3 | 9 / 2 | |
| 6.2.0 | 9 / 2 | |
| 6.1.20 | 9 / 2 | |
| 6.1.18 | 9 / 2 | |
| 6.1.17 | 9 / 2 | |
| 6.1.16 | 9 / 2 | |
| 6.1.15 | 9 / 2 | |
| 6.1.13 | 9 / 2 | |
| 6.1.12 | 9 / 2 | |
| 6.1.11 | 9 / 2 | |
| 6.1.10 | 9 / 2 | |
| 6.1.9 | 9 / 2 | |
| 6.1.8 | 9 / 2 | |
| 6.1.7 | 9 / 2 | |
| 6.1.6 | 9 / 2 | |
| 6.1.5 | 9 / 2 | |
| 6.1.4 | 9 / 2 | |
| 6.1.2 | 9 / 2 | |
| 6.0.19 | 9 / 2 | |
| 6.0.18 | 9 / 2 | |
| 6.0.15 | 9 / 2 | |
| 6.0.14 | 9 / 1 | |
| 6.0.12 | 9 / 1 | |
| 6.0.2 | 9 / 1 | |
| 6.0.0 | 9 / 1 |
v6.3.1
2 findings
HIGH
Publisher changed: sebmck → amasad (on 2015-12-01)
provenance
This version was published by a different npm account than previous versions on 2015-12-01. This could indicate a legitimate maintainer transition or an account compromise.
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.