rollup-plugin-node-resolve
Bundle third-party dependencies in node_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): Legitimate maintainer transition within the rollup org; lukastaegert is a core Rollup maintainer with extensive track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): lukastaegert is a known core Rollup maintainer; addition is a legitimate org-level transition. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 5 / 12 | |
| 5.1.1 | 5 / 12 | |
| 5.1.0 | 5 / 12 | |
| 5.0.4 | 5 / 12 | |
| 5.0.3 | 5 / 12 | |
| 5.0.2 | 5 / 12 | |
| 5.0.1 | 5 / 12 | |
| 5.0.0 | 5 / 12 | |
| 4.2.4 | 4 / 9 | |
| 4.2.3 | 4 / 9 | |
| 4.2.2 | 4 / 10 | |
| 4.2.1 | 4 / 10 | |
| 4.2.0 | 4 / 10 | |
| 4.1.0 | 4 / 10 | |
| 4.0.1 | 3 / 9 | |
| 4.0.0 | 3 / 9 | |
| 3.4.0 | 3 / 9 | |
| 3.3.0 | 3 / 9 | |
| 3.2.0 | 3 / 9 | |
| 3.1.0 | 3 / 9 | |
| 3.0.3 | 3 / 9 | |
| 3.0.2 | 3 / 9 | |
| 3.0.1 | 3 / 9 | |
| 3.0.0 | 4 / 9 | |
| 2.1.1 | 3 / 9 | |
| 2.1.0 | 3 / 9 | |
| 2.0.0 | 3 / 9 | |
| 1.7.3 | 3 / 9 | |
| 1.7.2 | 3 / 9 | |
| 1.7.1 | 3 / 9 | |
| 1.7.0 | 3 / 9 | |
| 1.6.0 | 3 / 9 | |
| 1.5.0 | 3 / 11 | |
| 1.4.0 | 3 / 11 |
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage 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.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-12-09. 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.