rollup-plugin-terser
Rollup plugin to minify generated es bundle
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 | missing-githead | AI (provenance): Legitimate publish environment change by the established maintainer trysound; no other malicious indicators present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): rollup-pluginutils is a well-known, legitimate Rollup ecosystem utility; its addition is consistent with the plugin's purpose. | ai | |
| dependencies | unvetted-dep:lave | AI (dependencies): lave is a small safe-serialization utility appropriate for minifier option handling. | ai | |
| provenance | no-provenance | AI (provenance): Established package from original maintainer; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() parses build-time options configuration, not untrusted network input. Legitimate for a minifier plugin. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 4 / 4 | |
| 7.0.1 | 4 / 4 | |
| 7.0.0 | 4 / 4 | |
| 6.1.0 | 4 / 4 | |
| 6.0.1 | 4 / 4 | |
| 6.0.0 | 4 / 4 | |
| 5.3.1 | 5 / 6 | |
| 5.3.0 | 5 / 6 | |
| 5.2.0 | 5 / 6 | |
| 5.1.3 | 5 / 6 | |
| 5.1.2 | 5 / 6 | |
| 5.1.1 | 5 / 6 | |
| 5.1.0 | 5 / 6 | |
| 5.0.0 | 4 / 6 | |
| 4.0.4 | 4 / 6 | |
| 4.0.1 | 5 / 8 | |
| 4.0.0 | 5 / 7 | |
| 3.0.0 | 4 / 7 | |
| 2.0.2 | 3 / 7 | |
| 2.0.1 | 3 / 7 | |
| 2.0.0 | 3 / 7 | |
| 1.0.1 | 2 / 7 | |
| 1.0.0 | 1 / 7 |
v7.0.1
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.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.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: trysound.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.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: trysound.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
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: trysound.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
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: trysound.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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: trysound.
[Accepted risk] 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: trysound.
[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
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: trysound.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.
v4.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.
v3.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.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.
v2.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.
v1.0.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.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.