soundings

Your package’s adoption, on one page, on your own box.

A timer reads every registry, appends the numbers, and rewrites one static page. No account, no database, nothing to keep running.

not released yet · v0.1 lands the week of 24 August

the chart last sounding 14:37 UTC
combernpm · 30-day downloads 4,127 +617
bourdonnpm · 30-day downloads 892 +62
getcomber/comber-pipeDocker Hub · pulls 2,206 +48
positif-aiPyPI · 30-day downloads 311 held 4h

A chart, mid-sounding. PyPI didn’t answer this cycle, so its last good reading is held rather than lost. Sample data.

Readings

Every number says whether it came back.

A source going quiet is normal. It should never take the page down, and it should never quietly hand you a stale number as if it were fresh.

4,127

Live

The source answered this cycle.

311 held 4h

Held

The source didn’t answer. The last good reading stays on the chart, dimmed and marked with how long it has been held.

no data

No reading

Nothing came back, and there is nothing to hold. Never shown as a zero — zero is a real measurement.

How it runs

A timer, a file, and a page.

You list your packages

Once. Names and the registries they live on — that is the whole configuration.

A sounding runs on a timer

Every source is read, and each reading is appended to a plain file on disk. A source that fails is held, not fatal — the timer never crashes.

The page is rewritten

One static HTML file, no JavaScript, no server. Serve it, or open it off disk.

Sources

Where the readings come from.

npm PyPI Docker Hub

More sources land as each one is proven against a real registry, rather than announced ahead of it.

There is no Soundings account.

The tool runs where you run it. Your numbers never leave the box, nothing here can rate-limit you or change its price, and if this site disappears tomorrow your chart still updates at half past the hour.