Libraries.io indexes data from9,279,084packages from32package managers. We monitor package releases, analyse each project's code, community, distribution and documentation, and we map the relationships between packages when they're declared as a dependency. The 'dependency tree' that emerges is the core of the services that we provide.
Spend your time including, not searching.
The majority of publication and distribution channels do not provide sufficient tools for developers to discover packages that could be valuable to them. Similarly they do not provide adequate information for individuals to judge the merit of one package over another when they tackle similar issues or solve similar problems.
Keeping a watch while you work.
The software we depend upon is constantly shifting and in need of continuous monitoring and management. By analysing packages and understanding the relationships between them, we can automate much of this.
Similarly we can help you maintain your open source package by reflecting the state of the ecosystem back at you. Exposing the network of consumers who depend upon your software and the characteristics of the packages your software is deployed within.
Smooth out version bumps.
Sign up, it's free for Open Source
Libraries.io tracks releases from9,279,084packages on32package managers in one place. Subscribe to a package and receive notifications of new versions or tags for platforms like Bower and Go that don't store release information centrally.
Libraries.io supports the following package managers. For more detail check outour compatibility matrix.
Some package managers require compilation before parsing their dependencies, some we simply haven't got around to yet. Luckily Libraries.io is an open source package so if you need to add a new package manager then you can. You can find everything you need to get started inour documentation.
Our goal is to raise the quality of all software, by raising the quality and frequency of contributions to free and open source software; the services, frameworks, plugins and tools we collectively refer to as libraries. We do this by tackling three problems:
If you’d like to know why we think this is the right approach then check out ourstrategy.
YES!Libraries.io is an inclusivecommunity of peopleworking together. So please, come on in.
Got a question or request for Libraries? Open anissue on GitHubor email[email protected]