@rollup/plugin-node-resolve
Locate and 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): guybedford is a well-known rollup ecosystem maintainer with a strong track record; this is a legitimate org-level handoff within the rollup/plugins monorepo, not a suspicious takeover. | ai | |
| dependencies | unvetted-dep:is-module | AI (dependencies): is-module is a well-known, stable utility used legitimately by this plugin for ES module detection. Not a risk. | ai | |
| dependencies | unvetted-dep:@types/resolve | AI (dependencies): @types/resolve is a TypeScript type definition package included as a runtime dep for type augmentation; standard pattern for rollup plugins. | ai | |
| phantom-deps | phantom-dep:@types/resolve | AI (phantom-deps): Framework-scoped type package; not directly imported but used for TypeScript type resolution. Expected pattern for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 16.0.3 | 5 / 9 | |
| 16.0.2 | 5 / 9 | |
| 16.0.1 | 5 / 9 | |
| 16.0.0 | 5 / 9 | |
| 15.3.1 | 5 / 9 | |
| 15.3.0 | 5 / 9 | |
| 15.2.4 | 5 / 9 | |
| 15.2.3 | 6 / 9 | |
| 15.2.2 | 6 / 9 | |
| 15.2.1 | 6 / 9 | |
| 15.2.0 | 6 / 9 | |
| 15.1.0 | 6 / 9 | |
| 15.0.2 | 6 / 9 | |
| 15.0.1 | 6 / 9 | |
| 15.0.0 | 6 / 9 | |
| 14.1.0 | 6 / 9 | |
| 14.0.1 | 6 / 9 | |
| 14.0.0 | 6 / 9 | |
| 13.3.0 | 6 / 9 | |
| 13.2.2 | 6 / 9 | |
| 13.2.1 | 6 / 9 | |
| 13.2.0 | 6 / 9 | |
| 13.1.3 | 6 / 9 | |
| 13.1.2 | 6 / 9 | |
| 13.1.1 | 6 / 9 | |
| 13.1.0 | 6 / 9 | |
| 13.0.6 | 6 / 9 | |
| 13.0.5 | 6 / 9 | |
| 13.0.4 | 6 / 9 | |
| 13.0.3 | 6 / 9 | |
| 13.0.2 | 6 / 9 | |
| 13.0.1 | 6 / 9 | |
| 13.0.0 | 6 / 9 | |
| 11.2.1 | 6 / 9 | |
| 11.2.0 | 6 / 9 | |
| 11.1.1 | 6 / 9 | |
| 11.1.0 | 6 / 9 | |
| 11.0.1 | 6 / 9 | |
| 11.0.0 | 6 / 9 | |
| 10.0.0 | 6 / 9 | |
| 9.0.0 | 6 / 9 | |
| 8.4.0 | 7 / 10 | |
| 8.1.0 | 7 / 9 | |
| 8.0.1 | 7 / 9 | |
| 8.0.0 | 7 / 9 | |
| 7.1.3 | 5 / 9 | |
| 7.1.2 | 5 / 9 | |
| 7.1.1 | 5 / 9 | |
| 7.1.0 | 5 / 9 | |
| 7.0.0 | 5 / 9 | |
| 6.1.0 | 5 / 9 |
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-05-04. 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.
v11.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-01-15. 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.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.