Connect Libraries.io to clariBI
Connect Libraries.io with your API key, choose the packages to track, and get dependency and popularity counts sitting next to the adoption and revenue they move with.
clariBI| Connection | API connector. You paste your Libraries.io API key. |
| Access | Read-only. clariBI never writes to Libraries.io. |
| 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 | 18 documented Libraries.io 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 Libraries.io
Libraries.io indexes open-source packages across dozens of ecosystems (npm, PyPI, Maven, RubyGems and more) and reports each one's popularity and how many other projects depend on it.
clariBI reads the Libraries.io API using your own API key: the current rank, star count, fork count, and dependent counts for the packages you choose. You type the "platform/name" pairs, and the connector reads the metadata read-only.
Vendor site: libraries.io
What clariBI syncs
clariBI pulls the current metadata for the packages you select through the Libraries.io API, lands it as a preprocessed dataset, and refreshes once the data is more than a day old. Access is read-only.
For each selected package, clariBI syncs the rank, stars, forks, and dependent counts, then builds an insights dashboard you can query, extend, or pull into reports. Each sync adds a fresh point, so the counts build into a trend over time.
clariBI only ever reads. It never changes anything on Libraries.io or in the underlying package registries.
What you can chart
- Current rank, stars, and forks per package
- Dependents and dependent-repository counts
- Growth between syncs as the counts accumulate
- Relative popularity across the packages you track
- Dependency reach next to your adoption or revenue
How to connect Libraries.io
Open Data Sources in clariBI
In clariBI, go to Data Sources > Add Data Source, find Libraries.io, and paste your Libraries.io API key (free from your account settings). The key is stored encrypted.
Choose packages
Type the packages to track in "platform/name" form (for example npm/react or pypi/requests). clariBI reads the metadata read-only.
Sync, then get dashboards
clariBI syncs the package metadata, preprocesses it, and builds an insights dashboard. Each sync records a fresh point, so the counts build into a trend, and clariBI reads them 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.
- "Is the package gaining dependents as fast as we are adding users?"
- "Did our latest release move the package's popularity rank?"
About the Libraries.io connector
What do I need to connect Libraries.io?
A free Libraries.io API key from your account settings. You paste it into clariBI once; it is stored encrypted, and there is no OAuth popup or app to register.
Does the connector give me a trend over time?
Libraries.io reports current metadata, not a daily series. clariBI records a fresh point on each sync, so the counts build into a trend the longer the source stays connected.
Which clariBI plans include Libraries.io?
Every plan can connect Libraries.io, 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 Libraries.io catalog need the trial or a Starter, Professional or Enterprise plan.
Try Libraries.io 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.