babel-core
Babel compiler core.
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): babel-core is a canonical compiler package; empty index.js is a known re-export pattern, not spam. | ai | |
| — | maintainer-removed | — | sean | |
| dependencies | unvetted-dep:regenerator-babel | AI (dependencies): regenerator-babel is a Babel-maintained fork of regenerator, an expected and intentional dependency of babel-core v4.x. Not suspicious. | ai | |
| dependencies | unvetted-dep:acorn-babel | AI (dependencies): acorn-babel is a Babel-maintained fork of acorn, an expected and intentional dependency of babel-core v4.x. Not suspicious. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): The eval() call in to-fast-properties.js is unreachable dead code after a return statement — a known V8 optimization trick used legitimately in Babel's internals. | ai | |
| phantom-deps | phantom-dep:path-is-absolute | AI (phantom-deps): path-is-absolute is a legitimate declared dependency; phantom-dep flag is a benign false positive for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from adding browser.min.js and browser-polyfill.min.js distribution bundles; expected for babel-core. | ai | |
| source-diff | net-exec-file:browser.min.js | AI (source-diff): Standard Browserify UMD bundle of Babel's browser build; require shims + new Function() for eval API are expected, not malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Babel 5→6 was a major architectural rewrite; large file count changes are expected across major versions of this package. | ai | |
| provenance | missing-githead | AI (provenance): Historical publish from 2015 by original author; gitHead metadata was inconsistent in early npm tooling. | ai | |
| source-diff | net-exec-file:lib/api/browser.js | AI (source-diff): Browser API for Babel: XHR loads source for transpilation, new Function() executes transpiled output. Core documented functionality of babel-core's browser entry point. | ai | |
| phantom-deps | phantom-dep:regenerator | AI (phantom-deps): Phantom dependency pattern is normal for build tools; regenerator is declared and used in config. | ai | |
| phantom-deps | phantom-dep:home-or-tmp | AI (phantom-deps): Phantom dependency pattern is normal for build tools; home-or-tmp is declared and used in config. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Phantom dependency pattern is normal for build tools; source-map-support is declared and used in config. | ai | |
| phantom-deps | phantom-dep:esutils | AI (phantom-deps): Phantom dependency pattern is normal for build tools; esutils is declared and used in config. | ai | |
| phantom-deps | phantom-dep:resolve | AI (phantom-deps): resolve is a legitimate dependency for dynamic module resolution in babel-core's plugin system. | ai | |
| phantom-deps | phantom-dep:bluebird | AI (phantom-deps): bluebird is a declared dependency used for promise handling in babel-core's async operations. | ai | |
| phantom-deps | phantom-dep:output-file-sync | AI (phantom-deps): output-file-sync is a declared dependency used for file writing operations in babel-core. | ai | |
| phantom-deps | phantom-dep:fs-readdir-recursive | AI (phantom-deps): fs-readdir-recursive is a declared dependency used for directory traversal in babel-core. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): The new babel-* deps reflect the well-documented Babel 5→6 modularization split; not a supply-chain injection. Stable for this package. | ai | |
| phantom-deps | phantom-dep:private | AI (phantom-deps): Phantom dependency pattern is normal for build tools; private is declared and used in config. | ai | |
| dependencies | unvetted-dep:bluebird | AI (dependencies): bluebird is a well-known Promise library with no malicious history; unvetted status is a system artifact, not a real risk for this package. | ai | |
| dependencies | unvetted-dep:core-js | AI (dependencies): core-js is a well-known, widely-used polyfill library with no malicious history; unvetted status is a system artifact, not a real risk for this package. | ai | |
| dependencies | unvetted-dep:convert-source-map | AI (dependencies): convert-source-map is a standard utility for source map handling; appropriate for a transpiler. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects Babel 6 modular architecture splitting monolith into separate packages; code moved to dependencies, not removed maliciously. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2018, predating Sigstore provenance; absence is expected for this era. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (danez, existentialism, hzoo, loganfsmyth, thejameskyle) are the official Babel core team; this is a documented legitimate transition. | ai | |
| provenance | publisher-changed | AI (provenance): Well-documented legitimate transfer from Sebastian McKenzie to the Babel team (loganfsmyth et al.) in 2018; not a suspicious takeover. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is necessary for transpiler to dynamically compile and execute code; input is from babel's own transform. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require for plugin loading is core transpiler functionality; plugins are resolved and validated before loading. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 6.24.0 | 19 / 3 | |
| 6.23.1 | 19 / 3 | |
| 6.14.0 | 21 / 3 | |
| 6.2.4 | 21 / 3 | |
| 6.2.1 | 21 / 3 | |
| 6.2.0 | 21 / 3 | |
| 6.1.21 | 25 / 3 | |
| 6.1.20 | 25 / 3 | |
| 6.1.19 | 25 / 3 | |
| 6.1.18 | 25 / 3 | |
| 6.1.17 | 25 / 3 | |
| 6.1.16 | 25 / 3 | |
| 6.1.15 | 25 / 3 | |
| 6.1.14 | 25 / 3 | |
| 6.1.13 | 25 / 3 | |
| 6.1.12 | 25 / 3 | |
| 6.1.11 | 25 / 3 | |
| 6.1.10 | 25 / 3 | |
| 6.1.9 | 25 / 3 | |
| 6.1.8 | 25 / 3 | |
| 6.1.7 | 25 / 3 | |
| 6.1.6 | 25 / 3 | |
| 6.1.5 | 25 / 3 | |
| 6.1.4 | 25 / 3 | |
| 6.1.2 | 24 / 1 | |
| 6.0.20 | 24 / 1 | |
| 6.0.19 | 24 / 1 | |
| 6.0.18 | 24 / 1 | |
| 6.0.17 | 24 / 1 | |
| 6.0.16 | 24 / 1 | |
| 6.0.15 | 24 / 1 | |
| 6.0.14 | 24 / 1 | |
| 6.0.12 | 24 / 1 | |
| 5.6.20 | 46 / 11 | |
| 5.6.19 | 46 / 11 | |
| 5.6.18 | 46 / 11 | |
| 5.6.16 | 48 / 11 | |
| 5.6.15 | 47 / 11 | |
| 5.6.14 | 48 / 11 | |
| 5.6.7 | 47 / 11 | |
| 5.6.6 | 47 / 11 | |
| 5.6.5 | 47 / 11 | |
| 5.6.4 | 47 / 11 | |
| 5.6.3 | 47 / 11 | |
| 5.6.2 | 47 / 11 | |
| 5.6.1 | 47 / 11 | |
| 5.5.8 | 34 / 11 | |
| 5.5.7 | 34 / 11 | |
| 5.5.6 | 34 / 11 | |
| 5.5.5 | 34 / 11 | |
| 5.5.4 | 34 / 11 |
v6.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hzoo) than the most recent previously approved version (loganfsmyth) on 2017-03-13, but hzoo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.23.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: loganfsmyth.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-14. This could indicate a legitimate maintainer transition or an account compromise.
v6.14.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hzoo.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-08-24. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.19
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.18
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: sebmck.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v6.0.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sebmck.
v5.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.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.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.