Libraries.io + 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.
Native Libraries.io data-source connector.
Paste your Libraries.io API key, pick the packages to track across any supported ecosystem, and clariBI syncs their dependency and popularity metadata into preprocessed datasets and auto-generated dashboards, right next to your other tools.
What is 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.
Learn more at libraries.io
Connect Libraries.io in three steps
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 Fernet-encrypted at rest.
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 the AI engine queries them alongside your business data.
What you can analyze
Out of the box with the Libraries.io connector:
- 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
- Cross-source: package popularity → sign-ups → revenue
Libraries.io is one of many data sources you can connect to clariBI. See the full list →
What gets synced
clariBI pulls the current metadata for the packages you select through the Libraries.io API, lands it as a preprocessed dataset, and refreshes on your schedule. 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.
Cross-source questions Libraries.io makes possible
Libraries.io data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Libraries.io × Adoption
"Is the package gaining dependents as fast as we are adding users?"
Planner: read the dependents count from Libraries.io across syncs, align to your active-user count by date, and report the two trends side by side.
Libraries.io × Releases
"Did our latest release move the package's popularity rank?"
Planner: read rank and stars from Libraries.io across syncs, mark your release dates, and report the change after each release.
Libraries.io connector FAQ
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 Fernet-encrypted at rest, 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 plan includes the Libraries.io connector?
Data-source connectors are available on the Trial, Starter, Professional, and Enterprise plans. You can connect Libraries.io during the free 14-day trial.
Start your free trial and connect Libraries.io in a minute
API key in, read-only, synced dashboards in seconds.
Start free trial