PUBLIC NPM DATA, IN PERSPECTIVE

Every package has
a growth story.

Explore download history. Spot sustained growth.
Follow the evidence behind the numbers.

01 / EXPLORE

A clear view of when
downloads changed.

A LITTLE CONTEXT GOES A LONG WAY

Look beyond the latest number.

Enter a package to see its download history,
growth signals, releases, and current dependent count.

↗ Dated download history◷ Transparent growth rule↓ Exportable evidence

02 / READ THE SIGNAL

Measured data.
Explicit interpretation.

01

A consistent growth rule

After eight complete Monday–Sunday weeks, look for four consecutive complete weeks each reaching the greater of twice the prior eight-week median or 25 downloads. The first qualifying week is an estimated onset within the selected history, not an explanation of its cause.

02

Honest boundaries

Daily history starts no earlier than January 10, 2015. Partial periods are marked; missing days stay missing. A launch or early rise may precede the required baseline. Downloads include repeated and automated activity; they do not count unique users.

03

Dependents are a snapshot

The current search-index count can include your own packages. npm does not document a comparable historical dependent-count series. Release timestamps can help reconstruct declared dependencies, but that is a separate analysis.