Is fetch-to-node safe to use?

fetch-to-node has no known vulnerabilities on the latest version (2.1.0). DepScope rates its health at 52/100 (high risk).

What is the latest version of fetch-to-node?

The latest version of fetch-to-node is 2.1.0, released 2025-04-26.

Does fetch-to-node have known vulnerabilities?

No known vulnerabilities on the latest version of fetch-to-node.

Is fetch-to-node deprecated?

No, fetch-to-node is actively maintained. Latest release: 2.1.0 (2025-04-26).

What are alternatives to fetch-to-node?

Popular alternatives to fetch-to-node in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does fetch-to-node use?

fetch-to-node is licensed under MIT.

fetch-to-node

npmv2.1.0

Node.js-compatible request and response objects for WinterTC runtimes

License MITpermissive2 versions1 maintainers0 deps124,313 weekly dl

mhart/fetch-to-node

/ 100

Health

use with caution

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

Moderate health score (52/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

14/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

27.9 KBminified

9.1 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/fetch-to-node