rollup-plugin-inject
Scan modules for global variables and inject `import` statements where necessary
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:shx | AI (dependencies): shx is a well-known cross-platform shell utility used only in build scripts (prebuild: shx rm -rf dist). It is not imported in runtime code; its presence as a runtime dep is a packaging oversight, not a security risk. | ai | |
| phantom-deps | phantom-dep:shx | AI (phantom-deps): shx is referenced only in npm scripts for build purposes, not imported in source code. This is expected behavior for a build utility. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected for this age cohort and not a risk signal. | ai | |
| dependencies | unvetted-dep:rollup-pluginutils | AI (dependencies): rollup-pluginutils is a legitimate Rollup ecosystem package maintained by the same team; stable dependency for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 3 / 5 | |
| 3.0.1 | 3 / 5 | |
| 3.0.0 | 3 / 5 | |
| 2.2.0 | 3 / 6 | |
| 2.1.0 | 5 / 4 | |
| 2.0.0 | 4 / 4 | |
| 1.4.1 | 4 / 4 | |
| 1.4.0 | 4 / 5 | |
| 1.3.0 | 4 / 5 | |
| 1.2.0 | 4 / 4 | |
| 1.1.1 | 4 / 6 | |
| 1.1.0 | 4 / 6 | |
| 1.0.0 | 4 / 6 |
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.