Gathering detailed insights and metrics for libp2p
Gathering detailed insights and metrics for libp2p
npm install libp2p
Typescript
Module System
Node Version
NPM Version
89.3
Supply Chain
98.9
Quality
96.4
Maintenance
100
Vulnerability
91.1
License
websockets: v9.1.1
Published on 07 Jan 2025
upnp-nat: v3.0.3
Published on 13 Dec 2024
config: v1.0.0
Published on 13 Dec 2024
webtransport: v5.0.21
Published on 12 Dec 2024
webrtc: v5.0.22
Published on 12 Dec 2024
circuit-relay-v2: v3.1.6
Published on 12 Dec 2024
TypeScript (99.07%)
JavaScript (0.8%)
Go (0.08%)
Makefile (0.04%)
Dockerfile (0.01%)
Total Downloads
3,848,219
Last Day
1,762
Last Week
13,706
Last Month
108,619
Last Year
970,713
2,372 Stars
6,574 Commits
453 Forks
69 Watching
53 Branches
222 Contributors
Latest Version
2.4.2
Package Id
libp2p@2.4.2
Unpacked Size
949.62 kB
Size
221.29 kB
File Count
159
NPM Version
10.9.2
Node Version
22.11.0
Publised On
12 Dec 2024
Cumulative downloads
Total Downloads
Last day
-1.1%
1,762
Compared to previous day
Last week
-48.6%
13,706
Compared to previous week
Last month
50.5%
108,619
Compared to previous month
Last year
15.6%
970,713
Compared to previous year
28
libp2p is the product of a long and arduous quest to understand the evolution of the Internet networking stack. In order to build P2P applications, devs have long had to make custom ad-hoc solutions to fit their needs, sometimes making some hard assumptions about their runtimes and the state of the network at the time of their development. Today, looking back more than 20 years, we see a clear pattern in the types of mechanisms built around the Internet Protocol, IP, which can be found throughout many layers of the OSI layer system, libp2p distils these mechanisms into flat categories and defines clear interfaces that once exposed, enable other protocols and applications to use and swap them, enabling upgradability and adaptability for the runtime, without breaking the API.
We are in the process of writing better documentation, blog posts, tutorials and a formal specification. Today you can find:
To sum up, libp2p is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradeability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.
The js-libp2p roadmap can be found here: https://github.com/libp2p/js-libp2p/blob/main/ROADMAP.md
It represents current projects the js-libp2p maintainers are focused on and provides an estimation of completion targets.
For all the information on how you can configure libp2p see CONFIGURATION.md.
For help configuring your node to resist malicious network peers, see LIMITS.md
If you are starting your journey with js-libp2p
, read the GETTING_STARTED.md guide.
You can find multiple examples on the examples repo that will guide you through using libp2p for several scenarios.
Clone and install dependencies:
1> git clone https://github.com/libp2p/js-libp2p.git 2> cd js-libp2p 3> npm install 4> npm run build
1# run all the unit tsts 2> npm test 3 4# run just Node.js tests 5> npm run test:node 6 7# run just Browser tests (Chrome) 8> npm run test:chrome
List of packages currently in existence for libp2p
This table is generated using the module
package-table
withpackage-table --data=package-list.json
.
Package | Version | Deps | CI | Coverage |
---|---|---|---|---|
libp2p | ||||
libp2p | ||||
@libp2p/interface | ||||
transports | ||||
@libp2p/tcp | ||||
@libp2p/webrtc | ||||
@libp2p/websockets | ||||
@libp2p/webtransport | ||||
secure channels | ||||
@chainsafe/libp2p-noise | ||||
@libp2p/plaintext | ||||
stream multiplexers | ||||
@libp2p/mplex | ||||
@chainsafe/libp2p-yamux | ||||
peer discovery | ||||
@libp2p/bootstrap | ||||
@libp2p/kad-dht | ||||
@libp2p/mdns | ||||
@chainsafe/discv5 | ||||
content routing | ||||
@libp2p/http-v1-content-routing | ||||
@libp2p/delegated-content-routing | ||||
@libp2p/kad-dht | ||||
peer routing | ||||
@libp2p/delegated-peer-routing | ||||
@libp2p/kad-dht | ||||
utilities | ||||
@libp2p/crypto | ||||
data types | ||||
@libp2p/peer-id | ||||
@libp2p/peer-record | ||||
pubsub | ||||
@ChainSafe/libp2p-gossipsub | ||||
@libp2p/floodsub |
And many others...
The libp2p implementation in JavaScript is a work in progress. As such, there are a few things you can do right now to help out:
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Stable Version
1
7.5/10
Summary
libp2p DoS vulnerability from lack of resource management
Affected Versions
< 0.38.0
Patched Versions
0.38.0
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
Found 3/29 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
branch protection not enabled on development/release branches
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-12-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More