node-request-retry

:guardsman: Wrap NodeJS request module to retry http requests in case of errors

Not yet testedsource: GitHubhomepageJavaScriptMITcommit 9d61cb22310b

JavaScript, MIT licensed. The project labels itself: http client, http requests and requests.

node-request-retry has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
346
forks
73
open issues
13
watchers
9
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

http-clienthttp-requestsrequests

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/node-request-retry.svg)](https://argusic.com/subject/node-request-retry)

Questions

Does node-request-retry run?
node-request-retry has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test node-request-retry?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for node-request-retry?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion