babel-plugin-transform-es2015-sticky-regex MIT 12 versions

babel-plugin-transform-es2015-sticky-regex

npm Repository

Compile ES2015 sticky regex to an ES5 RegExp constructor

12

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition from Babel creator (sebmck) to long-time Babel maintainer (hzoo); well-documented team handoff.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Tiny payload and mass-production signals are expected for Babel monorepo transform plugins; not spam indicators.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
6.24.1	3 / 1	2017-04-07
6.22.0	3 / 1	2017-01-20
6.8.0	3 / 1	2016-05-02
6.5.0	3 / 1	2016-02-07
6.3.13	3 / 1	2015-12-04
6.2.4	3 / 1	2015-11-25
6.1.18	3 / 1	2015-11-12
6.1.17	3 / 1	2015-11-12
6.1.4	3 / 1	2015-11-11
6.0.18	3 / 0	2015-11-03
6.0.14	3 / 0	2015-10-30
6.0.2	3 / 0	2015-10-29

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

1 finding

LOW No provenance attestation provenance

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

v6.8.0

1 finding

LOW No provenance attestation provenance

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

v6.5.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

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

v6.3.13

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

LOW No provenance attestation provenance

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

v6.1.18

1 finding

LOW No provenance attestation provenance

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

v6.1.17

1 finding

LOW No provenance attestation provenance

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

v6.1.4

1 finding

LOW No provenance attestation provenance

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

v6.0.18

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

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.