Connect npm to clariBI
Connect npm with no API key, choose the packages to track, and get daily download counts sitting next to the adoption and revenue they move with.
clariBI| Connection | API connector. No key or account needed. |
| Access | Read-only. clariBI never writes to npm. |
| Sync | When the data is more than a day old, clariBI syncs it again before a question, dashboard refresh or report uses it. You can also press Sync now. |
| More endpoints | 5 documented npm endpoints you can add, up to 30 per source (trial, Starter and above) |
| Plans | Every plan, including Free. Asking questions in plain English needs the trial or Starter and above. |
About npm
npm is the package registry for the JavaScript ecosystem, and it publishes an open download-counts API that reports how many times each package was installed per day.
clariBI reads the npm download-counts API: the daily download total for the packages you choose, over the history window you set. You type the package names, and the connector reads the counts read-only. No API key is required.
Vendor site: npmjs.com
What clariBI syncs
clariBI pulls daily download history for the packages you select through the open npm download-counts API, lands it as a preprocessed dataset, and refreshes it once it is more than a day old. Access is read-only.
For each selected package, clariBI syncs the daily download count, then builds an insights dashboard you can query, extend, or pull into reports.
clariBI only ever reads. The npm download-counts API is open, so there is no key or account to manage.
What you can chart
- Daily download count per package over your chosen window
- Download trend and week-over-week growth
- Relative adoption across the packages you track
- Spikes lined up with release or announcement dates
- Download momentum next to your funnel or revenue
How to connect npm
Open Data Sources in clariBI
In clariBI, go to Data Sources > Add Data Source and find npm. There is no API key to paste, so you go straight to choosing packages.
Choose packages and history
Type the package names to track (for example react, express, or your own published package) and choose how much history to pull. clariBI reads the download counts read-only.
Sync, then get dashboards
clariBI syncs the daily downloads, preprocesses them, and builds an insights dashboard. Ask "How did downloads of our package track our release dates?" and clariBI reads the synced counts alongside your business data.
Questions you can ask
Asking in plain English uses AI credits, so it needs the trial or a Starter, Professional or Enterprise plan. Totals and trends are computed from the synced rows; the AI plans the question, picks the chart and writes the explanation.
- "Did the spike in package downloads turn into product sign-ups?"
- "Which releases actually moved download volume?"
About the npm connector
Do I need an API key for npm?
No. The npm download-counts API is open with no API key. You type the package names in clariBI and the connector reads the counts read-only.
Can clariBI change anything in npm?
No. The connector only reads the public daily download counts for the packages you select. It never publishes or changes anything.
Which clariBI plans include npm?
Every plan can connect npm, within its data source limit: 3 on Free, 5 on Lite, 10 on Starter, 50 on Professional and 100 on Enterprise. Each source gets an automatic dashboard on every plan. Asking questions in plain English, AI reports and adding endpoints from the npm catalog need the trial or a Starter, Professional or Enterprise plan.
Try npm in clariBI
The trial lasts 14 days, includes 50 AI credits and needs no card. When it ends, your account moves to the Free plan and keeps its data and dashboards.