How Semverse works
Semverse is a free public tool for comparing npm package versions and reading their release notes. It brings the available sources together so you can review an update before changing your dependencies. No account, repository connection or API key is required.
How do I compare two npm versions?
- Search for a package, including scoped names such as @supabase/supabase-js.
- Open Compare versions and choose your current version and target version. Enable prereleases if you want to include alpha, beta, release-candidate or canary versions.
- Review the releases after your current version, up to and including your target. Filter breaking signals or missing history, and follow the original source links for context.
You can share the comparison link or copy its summary as Markdown.
Where do the release notes come from?
Package names and published versions come from the npm registry. Semverse looks for GitHub Releases and supported changelog files in the package’s public GitHub repository. When release notes are unavailable, it may show commit history between matching tags. Each available entry links to its source.
Semverse caches this information and checks sources as packages are visited. The last-checked time describes the source check; it is not the release date. A check may still be in progress or delayed by upstream limits. Repositories hosted outside GitHub can have version history without ingested release notes.
What is a breaking-change signal?
Signals flag changes worth reading: major-version changes, explicit breaking-change headings or statements, and terms such as removed or deprecated. They use version information and rules applied to source text, including conventions described by Semantic Versioning and Conventional Commits. Evidence excerpts let you inspect why a signal appeared.
Semverse does not inspect your application or use AI to determine compatibility. A signal may not affect your usage, and an update without signals can still require changes. Review the package’s migration guidance and test the update in your application.
What does missing history mean?
Missing history means Semverse has no usable notes or commit history for that release. It does not mean that nothing changed. Commit-only history is also less complete than a maintainer’s migration guide. Coverage indicators distinguish these gaps from available release notes.
Does Semverse install or update my packages?
No. Semverse is a reader for public package information. It does not connect to your private repositories, install dependencies or modify your code. Use your usual package manager and test workflow when you are ready to update.