@libp2p/interface-connection-encrypter 4.0.1-ab0e3980

Connection Encrypter interface for libp2p

@libp2p/interface-connection-encrypter@4.0.1-ab0e3980 was published on 2023-06-19. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @libp2p/interface-connection-encrypter versions · Permanent reference to 4.0.1-ab0e3980 · Latest release

Package specifications

Version4.0.1-ab0e3980
License declarationApache-2.0 OR MIT
Published2023-06-19T10:02:12.177Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size13.77 KiB
Published file count14
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars74
Repository forks26

Install @libp2p/interface-connection-encrypter 4.0.1-ab0e3980

npm install @libp2p/interface-connection-encrypter@4.0.1-ab0e3980
pnpm add @libp2p/interface-connection-encrypter@4.0.1-ab0e3980
yarn add @libp2p/interface-connection-encrypter@4.0.1-ab0e3980

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

Evidence and freshness