eslint-plugin-babel
an eslint rule plugin companion to babel-eslint
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from existentialism to kaicataldo is a routine Babel team handoff; both are known core contributors. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a well-known Babel core team member; legitimate maintainer addition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable ESLint plugin with infrequent releases; dormancy is expected for a mature package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged maintainers (sebmck, hzoo, loganfsmyth, danez) are all prominent Babel core team members; false positive. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 1 / 4 | |
| 5.3.0 | 1 / 4 | |
| 5.2.1 | 1 / 4 | |
| 5.2.0 | 1 / 4 | |
| 5.1.0 | 1 / 4 | |
| 5.0.0 | 1 / 4 | |
| 4.1.2 | 0 / 4 | |
| 4.1.1 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.1 | 0 / 4 | |
| 4.0.0 | 0 / 4 | |
| 3.3.0 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.2.0 | 1 / 5 | |
| 2.1.1 | 1 / 5 | |
| 2.1.0 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.2.0 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.0 | 1 / 6 |
v5.3.1
2 findingsThis version was published by a different npm account than previous versions on 2020-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-20. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.