node-fetch 2.4.0

A light-weight module that brings window.fetch to node.js

node-fetch@2.4.0 was published on 2019-04-26. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is 4.x || >=6.0.0.

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

Package specifications

Version2.4.0
License declarationMIT
Published2019-04-26T17:24:20.869Z
Node.js requirement4.x || >=6.0.0
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size148.38 KiB
Published file count8
Package typeNot declared
ES module entrylib/index.mjs
Default entrylib/index
Side effects declarationNot declared
Direct advisories2
Resolved graph dependencies0
Repository stars8846
Repository forks1056

Install node-fetch 2.4.0

npm install node-fetch@2.4.0
pnpm add node-fetch@2.4.0
yarn add node-fetch@2.4.0

Runtime dependencies

  • None declared

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.

    Known direct advisories

    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