@rollup/plugin-babel
Seamless integration between Rollup and Babel.
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 | missing-githead | AI (provenance): Monorepo publish tooling change; shellscape is a long-standing trusted publisher of the rollup org packages. | ai | |
| provenance | no-provenance | AI (provenance): Informational; many established packages lack Sigstore provenance. Not a risk signal for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 7.1.0 | 3 / 11 | |
| 7.0.0 | 2 / 11 | |
| 6.1.0 | 2 / 11 | |
| 6.0.4 | 2 / 11 | |
| 6.0.3 | 2 / 11 | |
| 6.0.2 | 2 / 11 | |
| 6.0.1 | 2 / 11 | |
| 6.0.0 | 2 / 11 | |
| 5.3.1 | 2 / 11 | |
| 5.3.0 | 2 / 11 | |
| 5.2.3 | 2 / 11 | |
| 5.2.2 | 2 / 11 | |
| 5.2.1 | 2 / 10 | |
| 5.2.0 | 2 / 10 | |
| 5.1.0 | 2 / 10 | |
| 5.0.4 | 2 / 9 | |
| 5.0.3 | 2 / 9 | |
| 5.0.2 | 2 / 9 | |
| 5.0.0 | 2 / 9 |
v7.1.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v6.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shellscape.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
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. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package 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.