libp2p-webrtc-direct 0.4.1

Dial using WebRTC without the need to set up any Signalling Rendezvous Point!

libp2p-webrtc-direct@0.4.1 was published on 2020-12-11. Its manifest declares 16 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All libp2p-webrtc-direct versions · Permanent reference to 0.4.1 · View npm registry JSON · Latest release

Package specifications

Version0.4.1
License declarationMIT
Published2020-12-11T12:31:38.422Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count16
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1563.15 KiB
Published file count41
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies214
Repository stars76
Repository forks18

Install libp2p-webrtc-direct 0.4.1

npm install libp2p-webrtc-direct@0.4.1
pnpm add libp2p-webrtc-direct@0.4.1
yarn add libp2p-webrtc-direct@0.4.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review2/10 — Found 7/27 approved changesets -- score normalized to 2
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — project is archived
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Security-Policy0/10 — security policy file not detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness