svgo
4.1.0 · 24 Aug 2026MIT52.3M / weekRepositoryHomepagenpmAtom feed
Upgrading svgo From 3.3.5 to 4.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 9
- changes to make
- 0
- advisories fixed
- 3
- new
- 14
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Deprecated4.0.0
Security
4 advisories still affect 4.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
- SVGO DoS through entity expansion in DOCTYPE (Billion Laughs)high · GHSA-xpqw-6gx7-v673
Upgrading to 4.1.0 clears them.
Release by release
- Breaking
Node.js v14 is no longer supported by the Node.js team, including security support, since 30 April 2023.
- Breaking
removeViewBox removes the scalability of SVGs.
- Breaking
removeTitle reduces accessibility, which preserving accessibility is more important than optimization.
- Breaking
svgo— for normal usage, such as scripts or server-side applications.
- Breaking
5 other lines we could not sort, mostly version bumps
- 4.0.0
convertColors, now converts all references to colors excluding references to IDs to lowercase. This can be disabled by setting
convertCasetofalse. - 4.0.0
convertColors, introduce parameter to convert colors to common casing (lowercase/uppercase).
- 4.0.0
removeEditorsNSData, include Boxy SVG namespace in the list of editor namespaces to remove.
- 4.0.0
removeEditorsNSData, include Krita namespace in the list of editor namespaces to remove.
- 4.0.0
We now generate our type declarations from JSDoc comments instead of maintaining them manually. Types will be much more accurate, include more documentation, and are guaranteed to be in sync with the implementation.
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.