@babel/compat-data
The compat-data to determine required Babel plugins
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with clear name and keywords; empty description is benign for data-only packages. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Legitimate build-time dependency used in scripts; phantom-dep pattern is expected for data processing utilities. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Legitimate build-time dependency used in scripts; phantom-dep pattern is expected for data processing utilities. | ai | |
| phantom-deps | phantom-dep:browserslist | AI (phantom-deps): Legitimate build-time dependency used in scripts; phantom-dep pattern is expected for data processing utilities. | ai | |
| provenance | publisher-changed | AI (provenance): Babel project transitioned to GitHub Actions CI/CD publishing; nicolo-ribaudo is a known core maintainer. Legitimate automation change. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo (Henry Zhu) is the original Babel creator; spam flag is a false positive for this package. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 0 / 3 | |
| 7.29.3 | 0 / 3 | |
| 7.29.0 | 0 / 3 | |
| 7.28.6 | 0 / 3 | |
| 7.28.5 | 0 / 3 | |
| 7.28.4 | 0 / 3 | |
| 7.28.0 | 0 / 3 | |
| 7.27.7 | 0 / 3 | |
| 7.27.5 | 0 / 3 | |
| 7.27.3 | 0 / 3 | |
| 7.27.2 | 0 / 3 | |
| 7.27.1 | 0 / 3 | |
| 7.26.8 | 0 / 3 | |
| 7.26.5 | 0 / 3 | |
| 7.26.3 | 0 / 3 | |
| 7.26.2 | 0 / 3 | |
| 7.26.0 | 0 / 3 | |
| 7.25.9 | 0 / 3 | |
| 7.25.8 | 0 / 3 | |
| 7.25.7 | 0 / 3 | |
| 7.25.4 | 0 / 3 | |
| 7.25.2 | 0 / 3 | |
| 7.25.0 | 0 / 3 | |
| 7.24.9 | 0 / 3 | |
| 7.24.8 | 0 / 3 | |
| 7.24.7 | 0 / 3 | |
| 7.24.6 | 0 / 3 | |
| 7.24.4 | 0 / 3 | |
| 7.24.1 | 0 / 3 | |
| 7.23.5 | 0 / 3 | |
| 7.23.3 | 0 / 3 | |
| 7.23.2 | 0 / 3 | |
| 7.22.20 | 0 / 3 | |
| 7.22.9 | 0 / 3 | |
| 7.22.6 | 0 / 3 | |
| 7.22.5 | 0 / 3 | |
| 7.22.3 | 0 / 3 | |
| 7.22.0 | 0 / 3 | |
| 7.21.9 | 0 / 3 | |
| 7.21.7 | 0 / 3 | |
| 7.21.5 | 0 / 3 | |
| 7.21.4 | 0 / 3 | |
| 7.21.0 | 0 / 3 | |
| 7.20.14 | 0 / 3 | |
| 7.20.10 | 0 / 3 | |
| 7.20.5 | 0 / 3 | |
| 7.20.1 | 0 / 3 | |
| 7.20.0 | 0 / 3 | |
| 7.19.4 | 0 / 3 | |
| 7.19.3 | 0 / 3 | |
| 7.19.1 | 0 / 3 | |
| 7.19.0 | 0 / 3 | |
| 7.18.13 | 0 / 3 | |
| 7.18.8 | 0 / 3 | |
| 7.18.6 | 0 / 3 | |
| 7.18.5 | 0 / 3 | |
| 7.17.10 | 0 / 3 | |
| 7.17.7 | 0 / 3 | |
| 7.17.0 | 0 / 3 | |
| 7.16.8 | 0 / 3 | |
| 7.16.4 | 0 / 3 | |
| 7.16.0 | 0 / 3 | |
| 7.15.0 | 0 / 3 | |
| 7.14.9 | 0 / 3 | |
| 7.14.7 | 0 / 3 | |
| 7.14.5 | 0 / 3 | |
| 7.14.4 | 0 / 3 | |
| 7.14.0 | 0 / 3 | |
| 7.13.15 | 0 / 3 | |
| 7.13.12 | 0 / 3 | |
| 7.13.11 | 0 / 4 | |
| 7.13.8 | 0 / 4 | |
| 7.13.6 | 0 / 4 | |
| 7.13.5 | 0 / 4 | |
| 7.13.0 | 0 / 4 | |
| 7.12.13 | 0 / 4 | |
| 7.12.7 | 0 / 3 | |
| 7.12.5 | 0 / 3 | |
| 7.12.1 | 0 / 3 | |
| 7.12.0 | 0 / 4 | |
| 7.11.0 | 3 / 4 | |
| 7.10.5 | 3 / 4 | |
| 7.10.4 | 3 / 4 | |
| 7.10.3 | 3 / 4 | |
| 7.10.1 | 3 / 4 | |
| 7.10.0 | 3 / 4 | |
| 7.9.6 | 3 / 4 | |
| 7.9.0 | 3 / 4 | |
| 7.8.6 | 3 / 4 | |
| 7.8.5 | 3 / 4 | |
| 7.8.4 | 3 / 4 | |
| 7.8.1 | 3 / 4 | |
| 7.8.0 | 3 / 4 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. 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.
v7.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.