← Home

@babel/helper-regex

npm Repository Homepage

Helper function to check for literal RegEx

9
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

danezexistentialismhzoojlhwungloganfsmythnicolo-ribaudo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both loganfsmyth and hzoo are well-known Babel core maintainers; this is a routine team rotation within the same project, not a suspicious takeover. ai
bogus-package bogus-package AI (bogus-package): This is a legitimate @babel monorepo helper package. Babel core team members (hzoo, loganfsmyth, danez) are not spam publishers; templated naming and tiny payload are expected for Babel helper packages. ai

Versions (showing 9 of 9)

Show 1 prerelease
Version Deps Published
7.10.5 1 / 0
7.10.4 1 / 0
7.10.1 1 / 0
7.8.3 1 / 0
7.8.0 1 / 0
7.5.5 1 / 0
7.4.4 1 / 0
7.4.3 1 / 0
7.0.0 1 / 0

v7.10.5

2 findings
HIGH Low-value / spam package indicators (4 signals, score 8) bogus-package

Matched 4 signal(s), weighted score 8: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hzoo, loganfsmyth, danez. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_KEYWORDS] No keywords declared. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 2462 bytes total.

LOW No provenance attestation provenance

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

v7.10.4

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: nicolo-ribaudo → jlhwung (on 2020-06-30) provenance

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

v7.10.1

1 finding
LOW No provenance attestation provenance

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

v7.8.3

1 finding
LOW No provenance attestation provenance

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

v7.8.0

1 finding
LOW No provenance attestation provenance

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

v7.5.5

1 finding
LOW No provenance attestation provenance

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

v7.4.4

1 finding
LOW No provenance attestation provenance

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

v7.4.3

2 findings
HIGH Publisher changed: loganfsmyth → nicolo-ribaudo (on 2019-04-02) provenance

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

v7.0.0

2 findings
HIGH Publisher changed: loganfsmyth → hzoo (on 2018-08-27) provenance

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