reqwest 2.0.3

A wrapper for asynchronous http requests

reqwest@2.0.3 was published on 2015-09-02. Its manifest declares 0 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 reqwest versions · Permanent reference to 2.0.3 · Latest release

Package specifications

Version2.0.3
License declarationMIT
Published2015-09-02T23:50:04.936Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./reqwest.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars2920
Repository forks331

Install reqwest 2.0.3

npm install reqwest@2.0.3
pnpm add reqwest@2.0.3
yarn add reqwest@2.0.3

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

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 8/29 approved changesets -- score normalized to 2
Binary-Artifacts9/10 — binaries present in source code
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License0/10 — license file not detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness