node-fetch 3.3.1

A light-weight module that brings Fetch API to node.js

node-fetch@3.3.1 was published on 2023-03-11. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^12.20.0 || ^14.13.1 || >=16.0.0.

All node-fetch versions · Permanent reference to 3.3.1 · Latest release

Package specifications

Version3.3.1
License declarationMIT
Published2023-03-11T10:47:49.391Z
Node.js requirement^12.20.0 || ^14.13.1 || >=16.0.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size104.59 KiB
Published file count17
Package typemodule
ES module entryNot declared
Default entry./src/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies5
Repository stars8846
Repository forks1056

Install node-fetch 3.3.1

npm install node-fetch@3.3.1
pnpm add node-fetch@3.3.1
yarn add node-fetch@3.3.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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy9/10 — security policy file detected
Code-Review10/10 — all changesets reviewed
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
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