Connect npm to clariBI
Connect npm to clariBI with no API key to sync daily package download counts for the packages you choose, read-only, with auto-generated dashboards next to your business data.
Connect npm to clariBI with no API key to sync daily package download counts for the packages you choose, read-only, with auto-generated dashboards next to your business data.
What is 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.
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 the AI engine queries the synced counts alongside your business data.
What you can analyze
- 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
- Cross-source: package downloads → sign-ups → revenue
What gets synced
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 on your schedule. 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.
Questions across your other data
Once your records are synced, the AI engine can join them to the rest of your business data. A few examples:
| Pairing | Question | How clariBI answers |
|---|---|---|
| npm × Sign-ups | "Did the spike in package downloads turn into product sign-ups?" | Planner: read daily downloads from npm, align to your sign-up count by date, and report the lag between adoption and conversion. |
| npm × Releases | "Which releases actually moved download volume?" | Planner: read the daily download series from npm, mark your release dates, and report the change in downloads after each release. |
Frequently asked questions
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.