web3-provider-engine

A JavaScript library for composing Ethereum provider objects using middleware modules

web3-provider-engine@17.0.1 was published on 2024-04-22. Its manifest declares 22 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^16.20 || ^18.16 || >=20.

All web3-provider-engine versions · Permanent reference to 17.0.1

Package specifications

Version17.0.1
License declarationMIT
Published2024-04-22T08:38:57.215Z
Node.js requirement^16.20 || ^18.16 || >=20
Type declarationsNot declared
Runtime dependency count22
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4137.72 KiB
Published file count74
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies226
Repository stars602
Repository forks320

Install web3-provider-engine 17.0.1

npm install web3-provider-engine@17.0.1
pnpm add web3-provider-engine@17.0.1
yarn add web3-provider-engine@17.0.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.

Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review10/10 — all changesets reviewed
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness