rollup-plugin-visualizer
Visualize and analyze your bundle to quickly see which modules are taking up space.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lib/flamegraph.js | AI (source-diff): rollup-plugin-visualizer ships minified frontend chart bundles (Preact + D3) as part of its HTML report generation. Minified dist files are expected and stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance attestation — this is a legitimate and security-improving transition for this well-established package. Generalizes to future versions published the same way. | ai | |
| source-diff | obfuscated-file:dist/lib/treemap-3d.js | AI (source-diff): This is a minified frontend bundle (Preact + Three.js) produced by rollup+terser as part of the 3D treemap visualization feature. Standard build output, not malicious obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by bundling Three.js (a large 3D graphics library) for the new treemap-3d visualization feature. Consistent with devDependency on 'three'. | ai |
Versions (showing 51 of 117)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 4 / 38 | |
| 7.0.0 | 4 / 36 | |
| 6.0.11 | 4 / 35 | |
| 6.0.8 | 4 / 35 | |
| 6.0.5 | 4 / 35 | |
| 6.0.4 | 4 / 35 | |
| 6.0.3 | 4 / 35 | |
| 6.0.1 | 4 / 35 | |
| 6.0.0 | 4 / 35 | |
| 5.14.0 | 4 / 35 | |
| 5.13.1 | 4 / 35 | |
| 5.13.0 | 3 / 36 | |
| 5.12.0 | 4 / 41 | |
| 5.11.0 | 4 / 41 | |
| 5.10.0 | 4 / 40 | |
| 5.9.3 | 4 / 40 | |
| 5.9.2 | 4 / 40 | |
| 5.9.1 | 4 / 40 | |
| 5.9.0 | 4 / 40 | |
| 5.8.3 | 3 / 34 | |
| 5.8.2 | 3 / 37 | |
| 5.8.1 | 4 / 37 | |
| 5.8.0 | 4 / 37 | |
| 5.7.1 | 4 / 37 | |
| 5.7.0 | 4 / 37 | |
| 5.6.0 | 4 / 36 | |
| 5.5.4 | 4 / 36 | |
| 5.5.2 | 4 / 37 | |
| 5.5.1 | 4 / 37 | |
| 5.5.0 | 4 / 37 | |
| 5.4.1 | 4 / 37 | |
| 5.4.0 | 4 / 37 | |
| 5.3.7 | 4 / 37 | |
| 5.3.6 | 4 / 37 | |
| 5.3.4 | 4 / 37 | |
| 5.3.3 | 4 / 37 | |
| 5.3.2 | 4 / 37 | |
| 5.3.1 | 4 / 37 | |
| 5.3.0 | 4 / 37 | |
| 5.2.1 | 4 / 37 | |
| 5.2.0 | 4 / 37 | |
| 5.1.0 | 4 / 37 | |
| 5.0.4 | 4 / 37 | |
| 5.0.3 | 4 / 37 | |
| 5.0.2 | 4 / 37 | |
| 4.2.2 | 4 / 20 | |
| 4.2.1 | 4 / 20 | |
| 4.2.0 | 4 / 19 | |
| 4.1.2 | 4 / 19 | |
| 4.1.1 | 5 / 19 | |
| 4.1.0 | 5 / 19 |
v7.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.