Announcing Knip v6
Learn what's new in Knip v6.
Learn what's new in Knip v6.
Three years in, Knip has found its place in over 10.000 projects and is downloaded over 18M times/month. A long period of steady growth in usage and stability allows Knip to become more accessible to more people. That’s why I’m excited and proud to introduce the brand new Editor Extension and MCP Server. For humans and coding agents alike, Knip will help keep your codebases tidy.
Don’t forget… Knip it before you ship it!
Honestly, Knip was a bit of a “cursed” project from the get-go. Getting anywhere
near a level of being broadly-ish valuable requires a good amount of
foolishness determination, and it has always been clear it would stay far
from perfect. It’s telling that most of similar projects have been
abandoned.
And even though Knip is in its infancy, this update is meant as a sign we feel we’re still on to something. External indicators include increased usage looking at numbers such as dependent repositories on GitHub and weekly downloads on npm, and bug reports about increasingly less rudimentary issues.
Exactly two years ago the first commit was pushed to GitHub and the first version of Knip was published to the npm registry. The name was initially Exportman! We’ve come a loooong way… The JavaScript ecosystem is highly dynamic and I’ve been crazy enough to even start, try and keep up with it! But here we are.
Learn what's new in Knip v5.
Learn what's new in Knip v4.
tl;dr; Memory usage is up to 50% lower, runs are up to 60% faster and you can start using v4 canary today. No “unused class members” for the time being, but this feature is planned to be restored.
ISC License © 2026Lars Kappert