Which Package Managers Does Libraries.io Support?

Libraries.io monitors open source packages across 32 different package managers, covering the major language ecosystems you are likely to use. If your stack relies on npm, PyPI, Maven, RubyGems, NuGet, or similar mainstream managers, it is almost certainly covered. The site maintains the authoritative, current list on its own pages, so treat any third-party summary as a starting point and confirm the exact set there.

What "supported" means on Libraries.io

Libraries.io is a free service that collects publicly available open source package information scraped from the internet. For each supported package manager, it indexes package metadata such as license, language, and repository links, and lets you search by those fields or browse new, trending, and popular packages.

Two practical consequences follow from how the data is gathered:

• Coverage is broad but not curated. The metadata is read from package and source repository metadata and is not validated for accuracy. It is fine for discovery and exploration, less so as the sole basis for compliance or risk decisions.
• The count moves. The platform reports monitoring roughly 11.9 million packages across those 32 managers, and both numbers change as ecosystems grow.

How to confirm your package manager is covered

1. Go to Libraries.io and open the search interface.
2. Search for a package you know exists in your ecosystem (for example, a well-known library from your language's registry).
3. If it returns a result with metadata such as license and repository, that manager is indexed.
4. To see the full set, look for the supported package managers list referenced from the site's own navigation or documentation.

The expected result is a package page showing license, language, dependencies, and repository information. If a known package returns nothing, that manager is likely outside the indexed set or the package is too new to have been scraped.

Common ecosystems and what to expect

The site's own materials name npm, PyPI, Maven, and RubyGems among the ecosystems it covers, alongside many others across 32 managers. In practice this means:

For any manager in the list, the same fields are available; there is no per-manager feature tier on the free service.

Where Libraries.io stops and Tidelift begins

If your goal is only to discover packages or check licenses, the free Libraries.io index is usually enough. If you need validated data for decisions about open source usage and management, the site itself points to the paid Tidelift Subscription, which provides curated, human-validated package data. The differences that matter for a package-manager question:

• License data: Libraries.io reads it from package metadata without validation; Tidelift analyzes and manually validates it, including normalized SPDX expressions.
• Dependency insights: Libraries.io offers limited, unvalidated insights; Tidelift provides extensive, human-validated insights including dependency graph relationships.
• Vulnerability insights: Not included in Libraries.io; Tidelift ingests CVE data from multiple sources and maps it to specific versions.
• Maintainer practices: Tidelift adds attestations such as 2FA status and security policy, which Libraries.io does not include.

So the package-manager coverage question has a simple answer for discovery work, and a different answer if you need accuracy guarantees: the free index covers 32 managers, while validated data for those same ecosystems sits behind the Tidelift Subscription.