@rollup/plugin-alias
Define and resolve aliases for bundle dependencies
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:slash | AI (phantom-deps): slash is a declared runtime dependency used in the built dist output; the phantom-dep finding reflects bundling rather than a real dependency issue. | ai | |
| provenance | no-provenance | AI (provenance): Established rollup org package with trusted publisher; lack of Sigstore attestation is a process gap, not a security risk for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-standing rollup official plugin by trusted publisher shellscape; dormancy followed by a legitimate major version bump (ESM-only, Node 20+, rollup 4+) is consistent with intentional major release cadence. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 0 / 5 | |
| 5.1.0 | 1 / 5 | |
| 5.0.1 | 1 / 5 | |
| 5.0.0 | 1 / 5 | |
| 4.0.4 | 1 / 5 | |
| 4.0.3 | 1 / 5 | |
| 4.0.2 | 1 / 5 | |
| 4.0.1 | 1 / 5 | |
| 4.0.0 | 1 / 5 | |
| 3.1.9 | 1 / 5 | |
| 3.1.8 | 1 / 5 | |
| 3.1.7 | 1 / 5 | |
| 3.1.6 | 1 / 5 | |
| 3.1.5 | 1 / 5 | |
| 3.1.4 | 1 / 5 | |
| 3.1.3 | 1 / 5 | |
| 3.1.2 | 1 / 5 | |
| 3.1.1 | 1 / 4 | |
| 3.1.0 | 1 / 4 | |
| 3.0.1 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.2.0 | 1 / 2 |
v5.1.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.
v5.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.
[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.