libp2p/libp2p: the umbrella repository for a peer-to-peer stack, where the code lives in a dozen other repositories
A modular and extensible networking stack which solves many challenges of peer-to-peer applications.
At a glance
- What is it?
- libp2p/libp2p holds the README, logos and community pointers for the libp2p peer-to-peer networking stack, not the stack itself. The implementations, from go-libp2p to c-libp2p, and the specifications each live in their own repositories with their own maintainers.
- Who is it for?
- Use this repository as a map: it tells you which implementation to open, where the specifications are and where to ask questions. Do not clone it expecting a library to build.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 20, 2026, and from our analysis. They are not legal advice.
Star history
- libp2p/libp2p3,174 ★ · +31
| Repository | 2026-09-25 | 2026-11-20 |
|---|---|---|
| libp2p/libp2p | 3.1k | 3.2k |
31 Stars in the last 56 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
There is no networking code in this repository
The top level of libp2p/libp2p is short: .github, .gitignore, ISSUE-LABELLING.md, LICENSE, README.md, funding.json, img and logo. There is no source directory, no build file and no package manifest. The primary language is not even detected.
So the repository is a front door. Its job is to describe libp2p, link to the formal specifications repository, list the active implementations and the dormant ones, give the security reporting route and gather the community channels. It also holds the issue labelling conventions in ISSUE-LABELLING.md.
The consequence is that cloning this repository gets you nothing to run. A developer who searches for libp2p and lands here has to take the next step and open the repository for their language. Likewise, the repository has no GitHub releases, so a version number for libp2p as a whole does not exist here; versions belong to each implementation.
A stack that lets applications use only the protocols they need
libp2p is described as a modular networking framework bundled together as a full stack of protocols for peer-to-peer systems. It positions itself as a network stack, a protocol suite, that cleanly separates concerns so that applications use only the protocols they need without giving up interoperability and upgradeability.
It grew out of IPFS into an independent project, designed to give any project state-of-the-art peer-to-peer capabilities. The project frames building large-scale peer-to-peer systems as complex and challenging for the last twenty years, and presents libp2p as a way to fix that.
For a reader this has a practical side. Modularity means you assemble a node from pieces, so the choice of transports and protocols is yours and the documentation for each piece lives at docs.libp2p.io. The cost is that there is no single default configuration to copy from this repository.
Twelve active implementations, run by different organisations
The active list is go-libp2p, js-libp2p for Node.js and the Browser, rust-libp2p which supports Wasm as well, py-libp2p, cpp-libp2p, swift-libp2p, nim-libp2p, jvm-libp2p for Kotlin as well, zig-libp2p, dotnet-libp2p, c-libp2p and litep2p, an alternative Rust implementation.
The owners differ. Several sit under the libp2p organisation, but swift-libp2p is under swift-libp2p, nim-libp2p under vacp2p, dotnet-libp2p under NethermindEth, zig-libp2p under zen-eth, c-libp2p under Pier-Two and litep2p under paritytech.
That spread affects you. Release cadence, feature coverage and support channels are set by each project, not by this umbrella. js-libp2p is the one that targets the browser, and rust-libp2p advertises Wasm support, so for a browser based peer those are the listed starting points. For anything else, compare the implementation repositories directly.
Two projects are named zig-libp2p, and the older one is unmaintained
The README separates active from dormant work. The dormant group holds erlang-libp2p and a zig-libp2p described as the original implementation, now unmaintained. The maintainers say they would love to help volunteers revive dormant projects, and invite people to reach out on any forum or chat room so they can start where the previous maintainers left off.
The naming is the trap. The active zig-libp2p lives under zen-eth, while the original sits under marcopolo, both with the same repository name. A package search or a quick GitHub search could send you to either one.
If you want Zig or Erlang, check which repository you have opened before building anything. For the active Zig one, the discussion section says there is no technical forum yet, so questions have nowhere implementation specific to go. Erlang users would be adopting an orphan.
Wire behaviour is defined in the specs repository, not here
The formal specifications of libp2p live in github.com/libp2p/specs. This repository only links to them.
That matters if you are mixing languages. When a Go node and a Rust node disagree, the question to settle is what the specification says, and then which implementation deviates. The README frames libp2p as a stack that keeps interoperability while allowing upgrades, and the specifications are where that interoperability is written down.
It also means that reading the umbrella repository will not tell you which protocols a given implementation supports. For that you need the implementation's own documentation, and the listing of twelve implementations in one place does not imply they have the same feature coverage. Check the one you pick against the specification before you rely on a feature.
Security reports go to an email address and should name the implementation
The security process is detailed on the discussions page at github.com/libp2p/libp2p/discussions/274. If you believe you have identified a security issue, report it to [email protected].
The report should include clear reproduction steps, the impacted implementations with examples given as go-libp2p, js-libp2p, py-libp2p and rust-libp2p, the expected versus observed behaviour, and the observed impact at network level or application level.
The point about naming implementations is practical. The umbrella project covers many codebases, so a report that says only libp2p leaves the maintainers guessing which repository is affected. Name each one that reproduces the problem, and state whether the effect is on the network or only within one application. Filing it as an ordinary public issue in an implementation is not the route the README describes.
Help is split across forums, four chat systems and a calendar
Community discussion about events, hackathons and conferences goes to discuss.libp2p.io, while technical help for a specific implementation goes to that implementation's GitHub Discussions. Links are given for go, js, rust, py, cpp, swift, jvm and dotnet. nim-libp2p points to a forum at forum.vac.dev, and zig-libp2p has no technical forum yet.
Chat is spread over the Filecoin Slack, with channels such as libp2p-community, libp2p-implementers, libp2p-docs and project-universal-connectivity, plus Discord, Telegram and Matrix. nim-libp2p and .NET libp2p have their own Discord and Telegram rooms.
Regular community meetings are published on a Lu.ma calendar with an iCal feed, and the community blog is at blog.libp2p.io. The repository is MIT licensed and its last push was on 2026-05-14, which is expected for an index; the activity that matters is in the implementations.
Editorial conclusion
Use this repository as a map: it tells you which implementation to open, where the specifications are and where to ask questions. Do not clone it expecting a library to build. Before choosing a language, open the implementation repository you are considering, check who maintains it and when it last changed, and read the specification where interoperability with other languages matters.
Frequently asked questions
What is libp2p?
libp2p is a modular networking framework bundled as a full stack of protocols for peer-to-peer systems, designed so applications use only the protocols they need.
How to use libp2p?
Pick an implementation such as go-libp2p, js-libp2p or rust-libp2p from the list, then follow docs.libp2p.io. This repository holds no code to install.
What is the difference between IPFS and libp2p?
libp2p grew out of IPFS into an independent project, built to give any project peer-to-peer capabilities rather than only serve IPFS.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/libp2p-libp2p)Star history chart for your README
[](https://hysenlabs.com/projects/libp2p-libp2p)Was this useful?