babel-standalone — Greenflagged

Standalone build of Babel for use in non-Node.js environments. Similar to the (now deprecated) babel-browser

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

daniel15danbuild

Keywords

babelbabeljs6to5transpiletranspiler

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): danbuild is Daniel15's CI/build account (same author: Daniel Lo Nigro). Transition from personal to build account is documented by matching GitHub repo and publisher history.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): danbuild is the same author's build account; addition is a legitimate same-person account transition, not a third-party takeover.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance; no-provenance is expected for this 2017-era package and not a risk signal.	ai	2026/04/24

Versions (showing 24 of 24)

Version	Deps	Published
6.26.0	0 / 117	2017-08-16
6.25.0	0 / 117	2017-06-08
6.24.2	0 / 117	2017-05-16
6.24.1	0 / 117	2017-05-14
6.24.0	0 / 116	2017-03-27
6.23.1	0 / 116	2017-02-15
6.22.1	0 / 116	2017-01-24
6.21.1	0 / 116	2017-01-03
6.21.0	0 / 115	2016-12-19
6.19.0	0 / 114	2016-11-17
6.18.2	0 / 114	2016-11-07
6.18.1	0 / 116	2016-10-29
6.18.0	0 / 116	2016-10-25
6.17.0	0 / 116	2016-10-04
6.15.0	0 / 116	2016-09-01
6.14.0	0 / 120	2016-08-27
6.13.2	0 / 101	2016-08-24
6.12.0	0 / 101	2016-08-02
6.10.3	0 / 95	2016-06-19
6.7.7	0 / 95	2016-04-24
6.7.4	0 / 95	2016-03-23
6.6.5	0 / 94	2016-03-06
6.4.4	0 / 92	2016-01-18
1.0.0	0 / 92	2015-12-06

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.25.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: daniel15 → danbuild (on 2017-06-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-08. This could indicate a legitimate maintainer transition or an account compromise.

v6.24.2

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

2 findings

HIGH Publisher changed: daniel15 → danbuild (on 2017-05-14) provenance

This version was published by a different npm account than previous versions on 2017-05-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.24.0

1 finding

INFO No provenance attestation provenance

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

v6.23.1

1 finding

LOW No provenance attestation provenance

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

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.21.1

1 finding

INFO No provenance attestation provenance

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

v6.21.0

1 finding

INFO No provenance attestation provenance

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

v6.19.0

1 finding

LOW No provenance attestation provenance

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

v6.18.2

1 finding

INFO No provenance attestation provenance

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

v6.18.1

1 finding

LOW No provenance attestation provenance

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

v6.18.0

1 finding

LOW No provenance attestation provenance

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

v6.17.0

1 finding

LOW No provenance attestation provenance

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

v6.15.0

1 finding

INFO No provenance attestation provenance

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

v6.14.0

1 finding

LOW No provenance attestation provenance

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

v6.13.2

1 finding

LOW No provenance attestation provenance

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

v6.12.0

1 finding

LOW No provenance attestation provenance

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

v6.10.3

1 finding

LOW No provenance attestation provenance

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

v6.7.7

1 finding

LOW No provenance attestation provenance

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

v6.7.4

1 finding

INFO No provenance attestation provenance

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

v6.6.5

1 finding

INFO No provenance attestation provenance

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

v6.4.4

1 finding

LOW No provenance attestation provenance

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