← Home

babel-helper-remap-async-to-generator

Helper function to remap async functions to generators

8
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): sebmck→hzoo is the documented Babel maintainer transition; stable for this package. ai
phantom-deps phantom-dep:babel-runtime AI (phantom-deps): babel-runtime is a declared dep used via Babel's transform output; stable FP. ai
maintainer-change maintainer-added AI (maintainer-change): amasad and thejameskyle are well-known Babel core team members; their addition is a legitimate and expected team expansion, not a suspicious takeover. ai
publish-pattern new-deps-added AI (publish-pattern): babel-template is a core Babel package from the same monorepo and author; adding it as a dependency in a Babel helper is expected and benign. ai
dependencies unvetted-dep:babel-traverse AI (dependencies): babel-traverse is a core Babel ecosystem package, widely trusted and used across millions of projects. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected for this era of Babel tooling and not a risk signal. ai

Versions (showing 8 of 8)

Version Deps Published
6.24.1 5 / 0
6.1.17 5 / 0
6.1.13 5 / 0
6.1.9 5 / 0
6.1.4 5 / 0
6.0.16 5 / 0
6.0.15 5 / 0
6.0.14 4 / 0

v6.24.1

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2017-04-07) provenance

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

INFO No provenance attestation provenance

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

v6.1.17

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

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
INFO No provenance attestation provenance

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

v6.1.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.0.16

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.