@babel/plugin-transform-duplicate-named-capturing-groups-regex
Compile regular expressions using duplicate named groups to index-based groups.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Babel publishes via GitHub Actions CI pipeline; lack of Sigstore provenance is consistent with their release process and not a risk indicator for this well-known package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 2 / 3 | |
| 7.29.0 | 2 / 3 | |
| 7.28.6 | 2 / 3 | |
| 7.27.1 | 2 / 3 | |
| 7.25.9 | 2 / 3 | |
| 7.25.7 | 2 / 3 | |
| 7.25.0 | 2 / 3 |
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.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.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.