web3 0.19.1
Ethereum JavaScript API, middleware to talk to a ethereum node over RPC
web3@0.19.1 was published on 2017-06-24. Its manifest declares 5 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 web3 versions · Permanent reference to 0.19.1 · Latest release
Package specifications
| Version | 0.19.1 |
|---|---|
| License declaration | LGPL-3.0 |
| Published | 2017-06-24T05:51:46.076Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./index.js |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 5 |
| Repository stars | 19908 |
| Repository forks | 5096 |
Install web3 0.19.1
npm install web3@0.19.1 pnpm add web3@0.19.1 yarn add web3@0.19.1
Runtime dependencies
- utf8 ^2.1.1
- xhr2 *
- crypto-js ^3.1.4
- bignumber.js ^4.0.2
- xmlhttprequest *
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.
- bignumber.js@4.1.0 — direct
- crypto-js@3.3.0 — direct
- utf8@2.1.2 — direct
- xhr2@0.2.1 — direct
- xmlhttprequest@1.8.0 — direct
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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — project is archived |
|---|---|
| Code-Review | 10/10 — all changesets reviewed |
| Security-Policy | 10/10 — security policy file detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 9/10 — license file detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/web3/0.19.1 — retrieved 2026-10-29T13:31:40.369Z
- https://api.deps.dev/v3/projects/github.com%2FChainSafe%2Fweb3.js — retrieved 2026-10-29T10:20:51.469Z
- https://api.deps.dev/v3/systems/npm/packages/web3/versions/0.19.1 — retrieved 2026-10-29T13:31:40.929Z
- https://api.deps.dev/v3/systems/npm/packages/web3/versions/0.19.1:dependencies — retrieved 2026-10-29T13:31:40.946Z