svgo
4.1.0 · 24 Aug 2026MIT52.3M / weekRepositoryHomepagenpmAtom feed
Upgrading svgo From 1.3.2 to 2.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 2
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.0.0
Security
3 advisories still affect 2.0.0
- SVGO removeScripts plugin leaves some executable scripts intacthigh · GHSA-2p49-hgcm-8545
- SVGO: removeScripts incompletely sanitizes executable HTML in SVG foreignObject elementsmoderate · GHSA-4vpr-x523-8j87
- SVGO: removeScripts allows executable links through namespace and control-character bypasseshigh · GHSA-w27v-7q3p-w38r
Upgrading to 2.8.4 clears them.
Release by release
- Breaking
YAML and JSON configuration is no longer supported for the sake of simplicity
- New
Added browser ready es module bundle
- New
Support only svgo.config.js for external configuration
- Breaking
3 other lines we could not sort, mostly version bumps
- 2.0.0
Smaller install size
- 2.0.0
Simplified config format
- 2.0.0
API is synchronous
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.