Gathering detailed insights and metrics for cross-fetch
Gathering detailed insights and metrics for cross-fetch
Universal WHATWG Fetch API for Node, Browsers and React Native.
Installations
npm install cross-fetchDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS, UMD
Node Version
20.18.1
NPM Version
10.8.2
Releases
26
Languages
5
JavaScript
TypeScript
HTML
Shell
Makefile
JavaScript (52.53%)
TypeScript (30.92%)
HTML (8.39%)
Shell (4.09%)
Makefile (4.07%)
Developer
lquixada
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
1,687 Stars
689 Commits
105 Forks
12 Watchers
8 Branches
19 Contributors
Updated on Jul 08, 2025
Maintainers
1
Package Meta Information
Latest Version
4.1.0
Package Id
cross-fetch@4.1.0
Unpacked Size
91.07 kB
Size
21.59 kB
File Count
13
NPM Version
10.8.2
Node Version
20.18.1
Published on
Dec 21, 2024
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
31
nycchainockhuskymochayargsrimrafrollupsemvercodecovexpresswebpackstandardcommitizentypescript@types/chai@types/nodebody-parserlint-stagedserve-indexwebpack-cli@types/mochawhatwg-fetch@commitlint/clistandard-versionrollup-plugin-copymocha-headless-chromerollup-plugin-esbuildcz-conventional-changelogrollup-plugin-esbuild-minify@commitlint/config-conventional
cross-fetch
Universal WHATWG Fetch API for Node, Browsers, Workers and React Native. The scenario that cross-fetch really shines is when the same JavaScript codebase needs to run on different platforms.
- Platform agnostic: browsers, Node or React Native
- Optional polyfill: it's up to you if something is going to be added to the global object or not
- Simple interface: no instantiation, no configuration and no extra dependency
- WHATWG compliant: it works the same way wherever your code runs
- TypeScript support: better development experience with types.
- Worker support: works on different types of workers such as Service Workers and CloudFlare Workers
Table of Contents
Install
1npm install --save cross-fetch
As a ponyfill (imports locally):
1// Using ES6 modules with Babel or TypeScript 2import fetch from 'cross-fetch'; 3 4// Using CommonJS modules 5const fetch = require('cross-fetch');
As a polyfill (installs globally):
1// Using ES6 modules 2import 'cross-fetch/polyfill'; 3 4// Using CommonJS modules 5require('cross-fetch/polyfill');
The CDN build is also available on unpkg:
1<script src="//unpkg.com/cross-fetch/dist/cross-fetch.js"></script>
This adds the fetch function to the window object. Note that this is not UMD compatible.
Usage
With promises:
1import fetch from 'cross-fetch'; 2// Or just: import 'cross-fetch/polyfill'; 3 4fetch('//api.github.com/users/lquixada') 5 .then(res => { 6 if (res.status >= 400) { 7 throw new Error("Bad response from server"); 8 } 9 return res.json(); 10 }) 11 .then(user => { 12 console.log(user); 13 }) 14 .catch(err => { 15 console.error(err); 16 });
With async/await:
1import fetch from 'cross-fetch'; 2// Or just: import 'cross-fetch/polyfill'; 3 4(async () => { 5 try { 6 const res = await fetch('//api.github.com/users/lquixada'); 7 8 if (res.status >= 400) { 9 throw new Error("Bad response from server"); 10 } 11 12 const user = await res.json(); 13 14 console.log(user); 15 } catch (err) { 16 console.error(err); 17 } 18})();
Demo & API
You can find a comprehensive doc at Github's fetch page. If you want to play with cross-fetch, check our JSFiddle playground.
Tip: Run the fiddle on various browsers and with different settings (for instance: cross-domain requests, wrong urls or text requests). Don't forget to open the console in the test suite page and play around.
FAQ
Yet another fetch library?
I did a lot of research in order to find a fetch library that could be simple, cross-platform and provide polyfill as an option. There's a plethora of libs out there but none could match those requirements.
Why polyfill might not be a good idea?
In a word? Risk. If the spec changes in the future, it might be problematic to debug. Read more about it on sindresorhus's ponyfill page. It's up to you if you're fine with it or not.
How does cross-fetch work?
Just like isomorphic-fetch, it is just a proxy. If you're in node, it delivers you the node-fetch library, if you're in a browser or React Native, it delivers you the github's whatwg-fetch. The same strategy applies whether you're using polyfill or ponyfill.
Who's Using It?
 |  |  |  |  |  |
|---|---|---|---|---|---|
| The New York Times | Apollo GraphQL | Swagger | VulcanJS | graphql-request |
Thanks
Heavily inspired by the works of matthew-andrews. Kudos to him!
License
cross-fetch is licensed under the MIT license © Leonardo Quixadá
Author
 |
|---|
| @lquixada |
Moderate
6.1/10
Summary
Incorrect Authorization in cross-fetch
Affected Versions
< 2.2.6
Patched Versions
2.2.6
Moderate
6.1/10
Summary
Incorrect Authorization in cross-fetch
Affected Versions
>= 3.0.0, < 3.1.5
Patched Versions
3.1.5
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 existing vulnerabilities detected
Reason
binaries present in source code
Details
- Warn: binary detected: examples/reactnative/android/gradle/wrapper/gradle-wrapper.jar:1
Reason
3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Reason
Found 0/29 approved changesets -- score normalized to 0
Reason
dangerous workflow patterns detected
Details
- Warn: untrusted code checkout '${{ github.event.pull_request.head.sha }}': .github/workflows/on-pull-request.yml:31
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/checks.yml:1
- Warn: no topLevel permission defined: .github/workflows/on-pull-request.yml:1
- Warn: no topLevel permission defined: .github/workflows/on-push-to-base-branch.yml:1
- Warn: no topLevel permission defined: .github/workflows/on-release.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:68: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:71: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/checks.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/checks.yml/v4.x?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/on-pull-request.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-pull-request.yml/v4.x?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/on-pull-request.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-pull-request.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-pull-request.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-pull-request.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-pull-request.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-pull-request.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-to-base-branch.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-push-to-base-branch.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-to-base-branch.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-push-to-base-branch.yml/v4.x?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/on-push-to-base-branch.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-push-to-base-branch.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-to-base-branch.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-push-to-base-branch.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-push-to-base-branch.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-push-to-base-branch.yml/v4.x?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/on-release.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:60: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:70: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/on-release.yml:82: update your workflow using https://app.stepsecurity.io/secureworkflow/lquixada/cross-fetch/on-release.yml/v4.x?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/checks.yml:34
- Warn: npmCommand not pinned by hash: .github/workflows/checks.yml:48
- Warn: npmCommand not pinned by hash: .github/workflows/checks.yml:62
- Warn: npmCommand not pinned by hash: .github/workflows/checks.yml:76
- Warn: npmCommand not pinned by hash: .github/workflows/on-pull-request.yml:43
- Warn: npmCommand not pinned by hash: .github/workflows/on-push-to-base-branch.yml:23
- Warn: npmCommand not pinned by hash: .github/workflows/on-push-to-base-branch.yml:50
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:38
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:46
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:54
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:62
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:72
- Warn: npmCommand not pinned by hash: .github/workflows/on-release.yml:88
- Info: 0 out of 23 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 4 third-party GitHubAction dependencies pinned
- Info: 0 out of 13 npmCommand dependencies pinned
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 4 are checked with a SAST tool
Score
3.2
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More