node-fetch 2.6.13
A light-weight module that brings window.fetch to node.js
node-fetch@2.6.13 was published on 2023-08-18. Its manifest declares 1 runtime dependency and 1 peer requirement. 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.6.13 · Latest release
Package specifications
| Version | 2.6.13 |
|---|---|
| License declaration | MIT |
| Published | 2023-08-18T20:24:16.578Z |
| Node.js requirement | 4.x || >=6.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 158.40 KiB |
| Published file count | 7 |
| Package type | Not declared |
| ES module entry | lib/index.mjs |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 8846 |
| Repository forks | 1056 |
Install node-fetch 2.6.13
npm install node-fetch@2.6.13 pnpm add node-fetch@2.6.13 yarn add node-fetch@2.6.13
Runtime dependencies
- whatwg-url ^5.0.0
Peer requirements
- encoding ^0.1.0 (optional peer)
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- tr46@0.0.3 — indirect
- webidl-conversions@3.0.1 — indirect
- whatwg-url@5.0.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.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Security-Policy | 9/10 — security policy file detected |
| Code-Review | 10/10 — all changesets reviewed |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/node-fetch/2.6.13 — retrieved 2026-10-29T07:15:26.409Z
- https://api.deps.dev/v3/projects/github.com%2Fnode-fetch%2Fnode-fetch — retrieved 2026-10-29T05:58:42.766Z
- https://api.deps.dev/v3/systems/npm/packages/node-fetch/versions/2.6.13 — retrieved 2026-10-29T07:15:26.903Z
- https://api.deps.dev/v3/systems/npm/packages/node-fetch/versions/2.6.13:dependencies — retrieved 2026-10-29T07:15:26.930Z