← Home

gulp-babel

Use next generation JavaScript, today

15
Versions
MIT
License
No
Install Scripts
Missing
Provenance

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

danezdemurgosexistentialismhzoologanfsmythsebmcksindresorhus

Keywords

gulppluginbabeltranspileres2015es2016es2017rewritingtransformationsyntaxcodegendesugaringjavascriptcompiler

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer from sindresorhus to hzoo (Babel project lead); well-documented maintainer transition within the Babel org. ai
maintainer-change maintainer-added AI (maintainer-change): hzoo is the Babel project lead; adding him as maintainer for a babel ecosystem package is expected. ai
provenance no-provenance AI (provenance): Published in 2017, before Sigstore provenance existed; not actionable for this package era. ai

Versions (showing 15 of 15)

Version Deps Published
8.0.0 4 / 9
7.0.1 4 / 8
7.0.0 4 / 7
6.1.3 6 / 7
6.1.2 6 / 6
6.1.1 6 / 6
6.1.0 6 / 6
6.0.0 6 / 6
5.3.0 6 / 3
5.2.1 6 / 3
5.2.0 6 / 2
5.1.0 6 / 2
5.0.0 5 / 2
4.0.1 5 / 2
4.0.0 5 / 2

v8.0.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: demurgos → loganfsmyth (on 2018-08-28) provenance

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

v7.0.1

1 finding
LOW No provenance attestation provenance

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

v7.0.0

2 findings
HIGH Publisher changed: sindresorhus → hzoo (on 2017-08-07) provenance

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