@rollup/plugin-replace
Replace strings in files while bundling
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 | missing-githead | AI (provenance): Established rollup official plugin; missing gitHead is a minor publish environment change, not a security signal. No code changes vs prior version. | ai | |
| provenance | no-provenance | AI (provenance): Established rollup official plugin published by a trusted long-standing maintainer; lack of Sigstore attestation is not a disqualifier for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 2 / 6 | |
| 6.0.2 | 2 / 6 | |
| 6.0.1 | 2 / 6 | |
| 6.0.0 | 2 / 6 | |
| 5.0.7 | 2 / 6 | |
| 5.0.6 | 2 / 6 | |
| 5.0.5 | 2 / 6 | |
| 5.0.4 | 2 / 6 | |
| 5.0.3 | 2 / 6 | |
| 5.0.2 | 2 / 6 | |
| 5.0.1 | 2 / 6 | |
| 5.0.0 | 2 / 6 | |
| 4.0.0 | 2 / 6 | |
| 3.1.0 | 2 / 6 | |
| 3.0.1 | 2 / 6 | |
| 3.0.0 | 2 / 6 | |
| 2.4.2 | 2 / 6 | |
| 2.4.1 | 2 / 6 | |
| 2.4.0 | 2 / 6 | |
| 2.3.4 | 2 / 6 | |
| 2.3.3 | 2 / 6 | |
| 2.3.2 | 2 / 6 | |
| 2.3.1 | 2 / 6 | |
| 2.3.0 | 2 / 6 | |
| 2.2.1 | 2 / 6 | |
| 2.2.0 | 3 / 5 |
v6.0.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
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.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: shellscape.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.