babel-plugin-add-module-exports
Fix babel/babel#2212
Supply chain provenance
Status for the latest visible version.
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
Keywords
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): 0.0.0 is the legitimate first version of this 10+ year old package with 1.2M weekly downloads; not indicative of malicious intent. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from 59naga to lijunle in 2019; lijunle is a long-standing trusted publisher and collaborator on the repo. | ai | |
| provenance | missing-githead | AI (provenance): ljharb is a highly trusted publisher; missing gitHead reflects a publish environment change, not a security concern. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security indicator for this well-established package from a trusted publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 0 / 27 | |
| 1.0.3 | 0 / 25 | |
| 1.0.2 | 0 / 25 | |
| 1.0.0 | 1 / 25 | |
| 0.3.3 | 1 / 22 | |
| 0.3.2 | 1 / 22 | |
| 0.3.1 | 0 / 22 | |
| 0.3.0 | 0 / 22 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 | |
| 0.1.4 | 1 / 17 | |
| 0.1.3 | 2 / 17 | |
| 0.1.2 | 2 / 12 | |
| 0.1.1 | 2 / 12 | |
| 0.1.0 | 1 / 11 | |
| 0.0.4 | 1 / 11 | |
| 0.0.3 | 1 / 11 | |
| 0.0.2 | 0 / 12 | |
| 0.0.1 | 0 / 12 | |
| 0.0.0 | 0 / 12 |
v1.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ljharb.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ljharb.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.2
3 findingsThis version was published by a different npm account than previous versions on 2019-04-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lijunle.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.