@babel/generator
Turns an AST into code.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/jsesc | AI (phantom-deps): Type-only packages are not directly imported; they are consumed by TypeScript tooling by convention. This is expected behavior for @types/* packages. | ai | |
| dependencies | unvetted-dep:@types/jsesc | AI (dependencies): @types/jsesc provides TypeScript types for jsesc, which is already a direct dependency. Including it as a runtime dep is unconventional but benign for a TypeScript-shipping package. | ai | |
| provenance | missing-githead | AI (provenance): Babel team changed their publish pipeline; missing gitHead is a process gap, not a security signal, for this well-established core package. | ai | |
| provenance | no-provenance | AI (provenance): Sigstore provenance was not yet standard practice for Babel at this version; no security risk given publisher track record and package history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation in the Babel project is routine; removal of developit does not indicate a takeover given the established team context. | ai | |
| provenance | publisher-changed | AI (provenance): jlhwung is a known Babel core team member; publisher rotation among Babel team members is normal for this monorepo package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jlhwung is a legitimate Babel core team member with a strong track record; addition is consistent with normal Babel team operations. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/parser and @jridgewell/* are well-known, legitimate Babel/source-map ecosystem packages; this dependency modernization is a routine refactor for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo (Henry Zhu) is the founder of Babel; spam flag is a false positive. No-keywords signal is irrelevant for a core Babel package. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): @babel/parser is a legitimate declared dependency in the Babel monorepo ecosystem; phantom-dep flag is a false positive for this package. | ai | |
| dependencies | unvetted-dep:jsesc | AI (dependencies): jsesc is a standard, well-known utility for escaping strings; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@babel/parser | AI (dependencies): @babel/parser is the official Babel parser from the same monorepo; a core and expected dependency for @babel/generator. | ai |
Versions (showing 48 of 148)
| Version | Deps | Published |
|---|---|---|
| 7.12.5 | 3 / 2 | |
| 7.12.1 | 3 / 2 | |
| 7.12.0 | 3 / 2 | |
| 7.11.6 | 3 / 2 | |
| 7.11.5 | 3 / 2 | |
| 7.11.4 | 3 / 2 | |
| 7.11.0 | 3 / 2 | |
| 7.10.5 | 3 / 2 | |
| 7.10.4 | 4 / 2 | |
| 7.10.3 | 4 / 2 | |
| 7.10.2 | 4 / 2 | |
| 7.10.1 | 4 / 2 | |
| 7.10.0 | 4 / 2 | |
| 7.9.6 | 4 / 2 | |
| 7.9.5 | 4 / 2 | |
| 7.9.4 | 4 / 2 | |
| 7.9.3 | 4 / 2 | |
| 7.9.0 | 4 / 2 | |
| 7.8.8 | 4 / 2 | |
| 7.8.7 | 4 / 2 | |
| 7.8.6 | 4 / 2 | |
| 7.8.4 | 4 / 2 | |
| 7.8.3 | 4 / 2 | |
| 7.8.0 | 4 / 2 | |
| 7.7.7 | 4 / 2 | |
| 7.7.4 | 4 / 2 | |
| 7.7.2 | 4 / 2 | |
| 7.7.0 | 4 / 2 | |
| 7.6.4 | 4 / 2 | |
| 7.6.3 | 4 / 2 | |
| 7.6.2 | 4 / 2 | |
| 7.6.0 | 5 / 2 | |
| 7.5.5 | 5 / 2 | |
| 7.5.0 | 5 / 2 | |
| 7.4.4 | 5 / 2 | |
| 7.4.0 | 5 / 2 | |
| 7.3.4 | 5 / 2 | |
| 7.3.3 | 5 / 2 | |
| 7.3.2 | 5 / 2 | |
| 7.3.0 | 5 / 2 | |
| 7.2.2 | 5 / 2 | |
| 7.2.0 | 5 / 2 | |
| 7.1.6 | 5 / 2 | |
| 7.1.5 | 5 / 2 | |
| 7.1.3 | 5 / 2 | |
| 7.1.2 | 5 / 2 | |
| 7.1.1 | 5 / 2 | |
| 7.0.0 | 5 / 2 |
v7.12.5
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: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.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: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.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: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.6
2 findingsThis version was published by a different npm account than previous versions on 2020-09-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.5
2 findingsThis version was published by a different npm account than previous versions on 2020-08-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.4
2 findingsThis version was published by a different npm account than previous versions on 2020-08-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jlhwung.
This version was published by a different npm account than previous versions on 2020-07-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
2 findingsThis version was published by a different npm account than previous versions on 2020-07-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
2 findingsThis version was published by a different npm account than previous versions on 2020-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.3
2 findingsThis version was published by a different npm account than previous versions on 2020-06-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.