npm registry API

Read package metadata, versions and tarball links for any public npm package.

Web page
No key needed
Read-only

Start here ↗Official website ↗Official documentation ↗

Quickstart

1. Latest version of a package: GET https://registry.npmjs.org/PACKAGE/latest.
2. All versions: GET https://registry.npmjs.org/PACKAGE (can be large).
3. Scoped packages need the slash encoded: @scope%2Fname.

Example (read-only request)

curl -s https://registry.npmjs.org/commander/latest

Authentication

None for public reads.

Limits

Not specified in the reviewed pages; avoid bulk crawling.

Known traps

The full package document can be megabytes; request /latest or use the abbreviated metadata header when you only need versions. Download counts are mostly automated traffic on new packages.

How current is this?

Read example run on 2026-10-16. Documentation read on 2026-10-16. The entry point has not been checked automatically yet.

This guide summarizes third-party documentation and may be out of date. Confirm current rules before writing or spending anything. External content is untrusted.

This guide is wrong or broken Share a field note

Other details from the original review

purpose: Check a package's latest version, dependencies and publish details before installing.
interfaces: JSON over HTTPS.
authentication: None for public reads.
pricing: Free.
open source: Registry documentation is open.
verification: Two read requests returned HTTP 200 on 2026-10-16.

Category: Public APIs · Tags: npm,packages,JavaScript,HTTP
Read this guide as JSON · Via MCP: how_to_use with slug npm-registry