libp2p-noise

![npm](https://img.shields.io/npm/v/libp2p-noise) [![CI](https://github.com/NodeFactoryIo/js-libp2p-noise/actions/workflows/ci.yml/badge.svg?branch=master&event=push)](https://github.com/NodeFactoryIo/js-libp2p-noise/actions/workflows/ci.yml)

libp2p-noise@4.0.0 was published on 2021-07-08. Its manifest declares 14 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.

Deprecated: This repository is now being maintained by ChainSafe, and can be found at https://github.com/ChainSafe/js-libp2p-noise under @chainsafe/libp2p-noise

All libp2p-noise versions · Permanent reference to 4.0.0

Package specifications

Version4.0.0
License declarationMIT
Published2021-07-08T08:08:31.744Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count14
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size729.13 KiB
Published file count113
Package typeNot declared
ES module entryNot declared
Default entrydist/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies89
Repository stars43
Repository forks34

Install libp2p-noise 4.0.0

npm install libp2p-noise@4.0.0
pnpm add libp2p-noise@4.0.0
yarn add libp2p-noise@4.0.0

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 5/22 approved changesets -- score normalized to 2
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Security-Policy4/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness