web3-providers 2.0.0-alpha.1

Web3 module to handle requests to external providers.

web3-providers@2.0.0-alpha.1 was published on 2019-08-06. Its manifest declares 11 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.0.

All web3-providers versions · Permanent reference to 2.0.0-alpha.1 · Latest release

Package specifications

Version2.0.0-alpha.1
License declarationLGPL-3.0
Published2019-08-06T19:25:54.237Z
Node.js requirement>=8.0.0
Type declarationsBundled declarations
Runtime dependency count11
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size154.55 KiB
Published file count6
Package typeNot declared
ES module entrydist/web3-providers.esm.js
Default entrydist/web3-providers.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies64
Repository stars19909
Repository forks5092

Install web3-providers 2.0.0-alpha.1

npm install web3-providers@2.0.0-alpha.1
pnpm add web3-providers@2.0.0-alpha.1
yarn add web3-providers@2.0.0-alpha.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.

Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review10/10 — all changesets reviewed
Maintained0/10 — project is archived
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-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness