@babel/runtime
babel's modular runtime helpers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Babel project transitioned to GitHub Actions CI/CD publishing; nicolo-ribaudo is a known core maintainer and this is a standard automation change. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @babel/runtime is a well-known, legitimate Babel scoped package. High semver on first publish, empty regenerator stub, and mass-production signals are all expected characteristics of this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 0 / 0 | |
| 7.29.2 | 0 / 0 | |
| 7.28.6 | 0 / 0 | |
| 7.28.4 | 0 / 0 | |
| 7.28.3 | 0 / 0 | |
| 7.28.2 | 0 / 0 | |
| 7.27.6 | 0 / 0 | |
| 7.27.4 | 0 / 0 | |
| 7.27.3 | 0 / 0 | |
| 7.27.1 | 0 / 0 | |
| 7.27.0 | 1 / 0 | |
| 7.26.10 | 1 / 0 | |
| 8.0.0-rc.3 | 0 / 0 | |
| 8.0.0-rc.2 | 0 / 0 | |
| 8.0.0-rc.1 | 0 / 0 | |
| 8.0.0-beta.4 | 0 / 0 | |
| 8.0.0-beta.3 | 0 / 0 |
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.
v8.0.0-rc.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0-rc.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0-rc.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0-beta.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. 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.
v8.0.0-beta.3
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.