Gathering detailed insights and metrics for @vercel/fetch-retry
Gathering detailed insights and metrics for @vercel/fetch-retry
Opinionated `fetch` (with retrying and DNS caching) optimized for use with Node.js
Installations
npm install @vercel/fetch-retryDeveloper Guide
BETA
Typescript
No
Module System
N/A
Releases
15
Languages
2
JavaScript
Shell
JavaScript (99.68%)
Shell (0.32%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
573 Stars
201 Commits
26 Forks
61 Watchers
1 Branches
97 Contributors
Updated on Apr 02, 2025
Maintainers
104
Package Meta Information
Latest Version
5.1.3
Package Id
@vercel/fetch-retry@5.1.3
Unpacked Size
12.39 kB
Size
4.23 kB
File Count
8
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
2
Peer Dependencies
1
Dev Dependencies
3
@vercel/fetch-retry
A layer on top of fetch (via node-fetch)
with sensible defaults for retrying to prevent common errors.
How to use
fetch-retry is a drop-in replacement for fetch:
1const fetch = require('@vercel/fetch-retry')(require('node-fetch')) 2 3module.exports = async () => { 4 const res = await fetch('http://localhost:3000') 5 console.log(res.status); 6}
Make sure to yarn add @vercel/fetch-retry in your main package.
Note that you can pass retry options to using opts.retry.
We also provide a opts.onRetry and opts.retry.maxRetryAfter options.
opts.onRetry is a customized version of opts.retry.onRetry and passes
not only the error object in each retry but also the current opts object.
opts.retry.maxRetryAfter is the max wait time according to the Retry-After header.
If it exceeds the option value, stop retrying and returns the error response. It defaults to 20.
Rationale
Some errors are very common in production (like the underlying Socket
yielding ECONNRESET), and can easily and instantly be remediated
by retrying.
The default behavior of fetch-retry is to attempt retries 10, 60
360, 2160 and 12960 milliseconds (a total of 5 retries) after
a network error, 429 or 5xx error occur.
The idea is to provide a sensible default: most applications should continue to perform correctly with a worst case scenario of a given request having an additional 15550ms overhead.
On the other hand, most applications that use fetch-retry instead of
vanilla fetch should see lower rates of common errors and fewer 'glitches'
in production.
Tests
To run rests, execute
1npm test
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/vercel/.github/SECURITY.md:1
- Info: Found linked content: github.com/vercel/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/vercel/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/vercel/.github/SECURITY.md:1
Reason
Found 8/15 approved changesets -- score normalized to 5
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/vercel/fetch/release.yml/main?enable=pin
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 23 are checked with a SAST tool
Reason
12 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
3.3
/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