@rollup/plugin-url
Import files as data-URIs or ES Modules
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 | publisher-changed | AI (provenance): lukastaegert is the primary Rollup maintainer; publisher change from shellscape is a known legitimate transition within the @rollup org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): @rollup/plugin-url lives in a monorepo with infrequent batch releases; dormancy is normal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Low-severity informational finding; no provenance is common for established packages not yet using Sigstore CI workflows. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 3 / 3 | |
| 8.0.1 | 3 / 3 | |
| 8.0.0 | 3 / 3 | |
| 7.0.0 | 3 / 3 | |
| 6.1.0 | 3 / 3 | |
| 6.0.0 | 3 / 3 | |
| 5.0.1 | 3 / 7 | |
| 5.0.0 | 3 / 7 | |
| 4.0.2 | 3 / 7 | |
| 4.0.1 | 3 / 7 | |
| 4.0.0 | 3 / 7 |
v8.0.2
2 findingsThis version was published by a different npm account than previous versions on 2023-10-05. 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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.