npm Popular Downloads Data API

Served from the CDN (2026-11-11). This endpoint's canonical address is https://cdn.dsh.so//data/npm-popular.json; the bytes come straight from Cloudflare R2. https://www.dsh.so/DATA_PATH still answers, but only as a 307 redirect to the same object — use the CDN address in new code. (Browser note: the CDN follows the bucket's CORS rules, which admit the www.dsh.so / dsh.so origins; curl and server-side clients are unaffected.)

One request returns the top 100 DSH plugins by all-time npm downloads — the popularity cut, sibling of the weekly ranking feed. total and week are the combined figures of two independently counted sources: the npm official registry plus the npmmirror (China) mirror — each item also carries the split in official / mirror.

Endpoints
URLDescriptionUpdate
https://cdn.dsh.so/data/npm-popular.jsonTop-100 plugins by cumulative npm downloads, one entry each, sorted by total (npm official + npmmirror mirror combined).rebuilt on each deploy; official totals from the cumulative accumulation, mirror totals from the mirror accumulation
https://cdn.dsh.so/data/npm-popular.schema.jsonJSON Schema for the feed format.stable

JSON endpoints allow cross-origin reads: Access-Control-Allow-Origin: *. No API key or registration is required.

Response fields
FieldTypeSemantics
generatedAtstring (ISO)Build timestamp — preserve it alongside any cached copy
totalsAsOfstring (YYYY-MM-DD) | nullLatest cumulative-total as-of date across the ranked entries; null when the feed is empty
sourcesobjectofficial / mirror, each with provider, api and semantics — the two counted streams behind the combined figures
scopeobjectInclusion criteria: listableOnly, ecosystemAppsExcluded, packagesWithBaselineOnly
limitnumber100 — the feed provides the top 100 entries only
countnumberNumber of ranked entries (≤ limit)
items[]arrayRanked entries, sorted by total descending (fields below)
items[].ranknumber1-based position in the ranking (1–100)
items[].idstringPlugin id (matches plugins.json ids and artifact slugs)
items[].namestringDisplay name
items[].packageNamestringnpm package name the downloads are counted on
items[].totalnumberCombined cumulative downloads = official total + mirror total, each = initial baseline + daily accumulation over its own window (official keeps ~18 months, mirror 2 years) — a combined figure is the sum of each source's own cumulative; never fabricated from partial daily sums. Split: official.total / mirror.total
items[].totalAsOfstring (YYYY-MM-DD) | nullAs-of date of this combined cumulative total (official baseline date, or the last day accumulated onto it; for a row whose total comes only from the mirror, the mirror as-of date)
items[].weeknumber | nullCombined weekly downloads, as context next to the all-time total = npm official last-week rolling window + the npmmirror mirror window (about 5 days fresher); null when neither source covers this package
items[].officialobject{ week, total } — the npm official (registry.npmjs.org) slice of this row; a field is null when official data is missing (never 0), and total can be null while the combined total is not
items[].mirrorobject{ week, total } — the npmmirror (registry.npmmirror.com) mirror slice. The mirror is an independently counted stream (not a proxy of the official numbers, so adding the two is not double counting), its window is about 5 days fresher than the official one, and it publishes no counting-rule statement — its counting semantics are defined by the mirror operator. Mirror totals are accumulated only for packages that have a mirror baseline (a partial daily sum is never passed off as a total), and null = mirror 404 / not collected yet, never 0
items[].starsnumberGitHub star count
items[].urlstringAbsolute plugin detail page URL
licenseobjectProvenance and reuse terms — aggregated from the public npm registry, attribution required

Honesty rule on coverage: only packages whose initial total baseline was ever collected (on the official side or the mirror side) can appear in this feed — packages never baselined are absent, never reported as 0. They join automatically once the next total-collection round covers them. There is no newly-indexed exclusion here: an all-time board needs none, fresh entries simply have small totals. On the mirror side, “no data” is expressed as null, never as 0, and a mirror total is only shown once a mirror baseline exists.

Usage

Fetch the top-100 popularity ranking (or open https://cdn.dsh.so/data/npm-popular.json in a browser):

curl https://cdn.dsh.so/data/npm-popular.json

The weekly-momentum counterpart is /data/npm-downloads.json. Per-plugin details (verification, security, install) join with /plugins-index.json or /plugin/@author/plugin.json on id.

The ranking is rebuilt on every deploy from the daily npm official Downloads API and npmmirror mirror snapshots plus the cumulative accumulations maintained by the dsh.so pipelines. Fields are add-only: existing fields will not be removed or renamed. Free to reference with attribution to dsh.so; new fields are announced in the changelog.

Was this page helpful?