babel-plugin-transform-simplify-comparison-operators
Convert === and !== to == and != if their types are inferred to be the same.
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): Legitimate transition from sebmck (Babel creator) to hzoo (long-time Babel core maintainer); well-documented handoff. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is a declared dependency referenced in config/build output; standard for Babel 5/6 era plugins. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo and loganfsmyth are legitimate Babel core team members; mass-production signal reflects the Babel monorepo structure; no-deps is expected for a simple transform plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established Babel ecosystem package predating Sigstore provenance; publisher has strong track record with 536 approved packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 6.9.4 | 0 / 0 | |
| 6.9.3 | 0 / 0 | |
| 6.9.2 | 0 / 0 | |
| 6.9.1 | 0 / 0 | |
| 6.9.0 | 0 / 0 | |
| 6.8.5 | 0 / 0 | |
| 6.8.4 | 0 / 0 | |
| 6.8.3 | 0 / 0 | |
| 6.8.2 | 0 / 0 | |
| 6.8.1 | 0 / 0 | |
| 6.8.0 | 1 / 1 | |
| 6.5.0 | 1 / 1 | |
| 6.3.13 | 1 / 1 | |
| 6.2.4 | 1 / 1 | |
| 6.1.18 | 1 / 1 | |
| 6.1.17 | 1 / 1 | |
| 6.1.4 | 1 / 1 | |
| 6.0.17 | 1 / 0 | |
| 6.0.14 | 1 / 0 | |
| 6.0.2 | 1 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v6.9.4
2 findingsMatched 3 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hzoo, loganfsmyth. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-07. 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.
v6.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.