Is upgraded-fetch-timeout safe to use?

upgraded-fetch-timeout has no known vulnerabilities on the latest version (0.0.3). DepScope rates its health at 33/100 (critical risk).

What is the latest version of upgraded-fetch-timeout?

The latest version of upgraded-fetch-timeout is 0.0.3, released 2024-02-26.

Does upgraded-fetch-timeout have known vulnerabilities?

No known vulnerabilities on the latest version of upgraded-fetch-timeout.

Is upgraded-fetch-timeout deprecated?

No, upgraded-fetch-timeout is actively maintained. Latest release: 0.0.3 (2024-02-26).

What are alternatives to upgraded-fetch-timeout?

Popular alternatives to upgraded-fetch-timeout in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does upgraded-fetch-timeout use?

upgraded-fetch-timeout is licensed under MIT.

upgraded-fetch-timeout

npmv0.0.3

HTTP/S fetch wrapper that adds the possibility to set a timeout after which a custom error is returned.

License MITpermissive3 versions1 maintainers0 deps92 weekly dl

/ 100

Health

use with caution

[email protected] low health (33/100) — consider alternatives

Moderate health score (33/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/upgraded-fetch-timeout