babel-plugin-module-resolver MIT 24 versions

babel-plugin-module-resolver

npm Repository Homepage

Module resolver plugin for Babel

24

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

tleunenfatfisz

Keywords

babelbabel-pluginmoduleresolveraliasrewriteresolverenamemappingrequireimport

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Version 0.0.1 is a known placeholder/stub release by a trusted publisher with a long track record. The signals reflect an empty initial commit, not malicious intent.	ai	2026/04/22
npm-metadata	no-description	AI (npm-metadata): Empty description is consistent with a stub initial release by a legitimate publisher; not indicative of malice for this package.	ai	2026/04/22
dependencies	unvetted-dep:find-babel-config	AI (dependencies): find-babel-config is a natural, expected companion dependency for babel-plugin-module-resolver; it locates Babel config files and is not suspicious in this context.	ai	2026/04/21

Versions (showing 24 of 24)

Version	Deps	Published
5.0.2	5 / 17	2024-04-18
5.0.1	5 / 17	2024-04-17
5.0.0	5 / 17	2023-01-09
4.1.0	5 / 17	2020-12-15
4.0.0	5 / 17	2019-12-11
3.2.0	5 / 17	2019-02-11
3.1.3	5 / 17	2019-01-21
3.1.2	5 / 17	2019-01-16
3.1.1	5 / 17	2018-03-24
3.1.0	5 / 13	2018-02-14
3.0.0	5 / 13	2017-11-08
2.7.1	3 / 10	2017-05-16
2.7.0	3 / 10	2017-03-30
2.6.2	3 / 12	2017-03-30
2.6.1	3 / 12	2017-03-29
2.6.0	3 / 12	2017-03-29
2.5.0	3 / 10	2017-02-05
2.4.0	3 / 10	2016-11-30
2.3.0	3 / 10	2016-11-06
2.2.0	2 / 13	2016-08-27
2.1.1	1 / 12	2016-08-22
2.1.0	1 / 12	2016-08-19
2.0.0	0 / 12	2016-08-14
0.0.1	0 / 0	2016-08-14

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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

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

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.7.1

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.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.

v2.3.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.

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

v2.1.1

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.

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

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

v0.0.1

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.