Loading page
About this tool
Check package versions quickly and compare updates instantly.
The Package Version Checker queries the public npm registry API (registry.npmjs.org) directly from your browser and reads the package's dist-tags.latest field — the exact version npm resolves to when you run npm install without a version range. Along with the version number it returns the package description, the registry's last-modified date, the author name recorded in the package metadata, and a link to the project homepage or docs when the package declares one. Scoped names like @angular/core work because the package name is URL-encoded before the request, and every lookup retries up to three times with a short backoff so a dropped connection doesn't come back as a false "not found".
Open Package Version Checker on AltFTool — it loads instantly in your browser.
Type an npm package name — react, lodash, or a scoped name like @angular/core.
Press Check Version to query the npm registry live.
Read the latest version, last-updated date, author, and docs link in the result card.
The version comes from dist-tags.latest in the registry metadata — the same value npm view <package> version returns, not a scraped or cached number.
@angular/core, @types/node and other scoped names are URL-encoded before the request, so they resolve exactly like unscoped ones.
Each lookup makes up to three attempts with a 0.5s then 1s backoff, so a flaky connection doesn't surface a false "package not found".
The request goes from your browser straight to the public registry — no npm login, no package.json upload, and no account.
Type the package name and press Check Version. The tool requests registry.npmjs.org/<package> and reads dist-tags.latest — the same version npm view react version reports and the version npm install react would resolve to.
Live. Every check fires a fresh request to the npm registry when you press the button, so the result reflects the current dist-tags.latest at that moment rather than a number stored in this page.
Yes. Enter the full scoped name including the @ and the slash — the name is URL-encoded before it's sent, so @angular/core and @types/node resolve the same way unscoped packages do.
No. This checker queries the npm registry only, so Python, Java, and .NET package names won't resolve. Use it for anything published to npmjs.com, including scoped and monorepo packages.
No — it returns the single latest published version, plus the description, last-updated date, author, and homepage link. For every published release, run npm view <package> versions in a terminal.
That appears after three failed attempts, usually because of a typo or a package that is unpublished or private. Note that the name you type is lowercased before the lookup, so a legacy package published with capital letters is checked in its all-lowercase form — read the returned description to confirm it's the package you meant.
It's the registry's time.modified value for the package — the last time its metadata changed, which is normally the most recent publish. It's a quick signal of whether a dependency is still being released.
Yes — free, no account, and no npm login. The only thing sent anywhere is the package name you type, and it goes to the public npm registry; nothing is stored on AltFTool.