babel-helper-evaluate-path MIT 10 versions

babel-helper-evaluate-path

npm Repository Homepage

path.evaluate wrapped in a try catch

10

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

babeljsboopathidanezexistentialismhzoologanfsmythvignesh.shanmugam

Keywords

babel-minifybabel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): Version 0.0.0 is a known pattern in the babel/babili monorepo for helper packages. Package is 9+ years old with 543k weekly downloads — not a throwaway.	ai	2026/04/24
npm-metadata	no-description	AI (npm-metadata): Missing description is a cosmetic issue; package is a well-established babel helper with clear purpose from its name and repository link.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate transfer from kangax to boopathi (package author) within the Babel project; both are known Babel contributors.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Added maintainers are all well-known Babel core team members (sebmck, loganfsmyth, danez, etc.); official org onboarding.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Tiny helper package by design; no deps and small payload are expected for a single-purpose Babel helper.	ai	2026/04/24

Versions (showing 10 of 10)

Version	Deps	Published
0.5.0	0 / 0	2018-09-24
0.4.3	0 / 0	2018-05-14
0.4.2	0 / 0	2018-05-14
0.4.1	0 / 0	2018-05-03
0.4.0	0 / 0	2018-04-08
0.3.0	0 / 0	2018-01-31
0.2.0	0 / 0	2017-08-14
0.1.0	0 / 0	2017-05-22
0.0.3	0 / 0	2016-11-18
0.0.0	0 / 0	2016-11-02

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

2 findings

HIGH Publisher changed: kangax → boopathi (on 2017-05-22) provenance

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

v0.0.3

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.

v0.0.0

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.