babel-helper-mark-eval-scopes MIT 11 versions

babel-helper-mark-eval-scopes

npm Repository Homepage

Mark scopes for deopt which contain a direct eval call

11

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

amasadbabeljsboopathihzookangaxloganfsmythvignesh.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): Package is ~9 years old, published by trusted Babel contributor boopathi under the official babel/babili repo. Version 0.0.0 is a known pattern in Babel monorepo helper packages, not a malware indicator.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
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.1	0 / 0	2017-05-22
0.1.0	0 / 0	2017-05-22
0.0.3	0 / 0	2017-03-03
0.0.2	0 / 0	2017-02-08
0.0.0	0 / 0	2017-01-19

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

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

1 finding

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding

LOW No provenance attestation provenance

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

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.