babel-cli MIT 15 versions

babel-cli

npm Repository Homepage

Babel command line.

15

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

thejameskylesebmckdanezhzoologanfsmyth

Keywords

6to5babeles6transpiletranspilerbabel-clicompiler

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-removed	AI (maintainer-change): amasad/jmm removal consistent with historical Babel team changes; no malicious indicators.	ai	2026/05/22
semgrep	semgrep:child-process-import	AI (semgrep): babel-node legitimately spawns child processes to pass V8 flags; stable pattern across all versions.	ai	2026/05/22
semgrep	semgrep:child-process-spawn	AI (semgrep): babel-node re-spawns itself with V8 flags via spawn; documented and expected behavior.	ai	2026/05/22
maintainer-change	maintainer-added	AI (maintainer-change): danez is a known Babel core contributor; addition consistent with Babel team evolution.	ai	2026/05/22
provenance	publisher-changed	AI (provenance): Both loganfsmyth and hzoo are core Babel maintainers; this is a legitimate team publish, not a takeover.	ai	2026/04/24
dependencies	unvetted-dep:request	AI (dependencies): request is a well-known HTTP library used legitimately in babel-cli for network calls; stable false positive for this package.	ai	2026/04/24
dependencies	unvetted-dep:v8flags	AI (dependencies): v8flags is a well-known utility for enumerating V8 flags, used legitimately by babel-node; stable false positive for this package.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in babel-doctor reads package.json from a known path to retrieve version info — standard diagnostic pattern, not arbitrary module loading.	ai	2026/04/24

Versions (showing 15 of 15)

Version	Deps	Published
6.26.0	15 / 1	2017-08-16
6.24.1	15 / 1	2017-04-07
6.24.0	15 / 1	2017-03-13
6.23.0	15 / 1	2017-02-14
6.22.2	15 / 1	2017-01-20
6.22.1	15 / 1	2017-01-20
6.1.9	20 / 1	2015-11-12
6.1.8	20 / 1	2015-11-12
6.1.5	20 / 1	2015-11-12
6.1.2	19 / 0	2015-11-05
6.1.1	18 / 0	2015-11-03
6.1.0	18 / 0	2015-11-03
6.0.15	15 / 0	2015-11-01
6.0.14	15 / 0	2015-10-30
6.0.12	15 / 0	2015-10-30

v6.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.24.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.24.0

2 findings

HIGH Publisher changed: loganfsmyth → hzoo (on 2017-03-13) provenance

This version was published by a different npm account than previous versions on 2017-03-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.23.0

2 findings

HIGH Publisher changed: hzoo → loganfsmyth (on 2017-02-14) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.22.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: hzoo → loganfsmyth (on 2017-01-20, known maintainer) provenance

This version was published by a different npm account (loganfsmyth) than the most recent previously approved version (hzoo) on 2017-01-20, but loganfsmyth 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.22.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.