Is fetch-multipart-graphql safe to use?

fetch-multipart-graphql has no known vulnerabilities on the latest version (2.3.1). DepScope rates its health at 51/100 (high risk).

What is the latest version of fetch-multipart-graphql?

The latest version of fetch-multipart-graphql is 2.3.1, released 2025-03-17.

Does fetch-multipart-graphql have known vulnerabilities?

No known vulnerabilities on the latest version of fetch-multipart-graphql.

Is fetch-multipart-graphql deprecated?

No, fetch-multipart-graphql is actively maintained. Latest release: 2.3.1 (2025-03-17).

What are alternatives to fetch-multipart-graphql?

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

What license does fetch-multipart-graphql use?

fetch-multipart-graphql is licensed under MIT.

fetch-multipart-graphql

npmv2.3.1

Cross browser function to fetch and parse streaming multipart graphql responses.

License MITpermissive33 versions2 maintainers0 deps2,524 weekly dl

relay-tools/fetch-multipart-graphql

/ 100

Health

use with caution

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

Moderate health score (51/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

3/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/fetch-multipart-graphql