Is Fetch Client Node Sdk Safe?

Fetch Client Node Sdk — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-26.

Exercise caution with Fetch Client Node Sdk. Fetch Client Node Sdk is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Fetch Client Node Sdk safe?

NO — USE WITH CAUTION — Fetch Client Node Sdk has a Nerq Trust Score of 48.2/100 (D). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Security Analysis → Fetch Client Node Sdk Privacy Report →

What is Fetch Client Node Sdk's trust score?

Fetch Client Node Sdk has a Nerq Trust Score of 48.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Fetch Client Node Sdk?

Fetch Client Node Sdk's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 0/100 — community adoption

What is Fetch Client Node Sdk and who maintains it?

Authorahpoi
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Fetch Client Node Sdk vs react-library-boilerplate-for-npmFetch Client Node Sdk vs bindlerFetch Client Node Sdk vs @yassidev/nuxt-directus

Safety Guide: Fetch Client Node Sdk

What is Fetch Client Node Sdk?

Fetch Client Node Sdk is a Node.js package — A wrapper around `isomorphic-fetch` that provides utility functions.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=fetch-client-node-sdk

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Fetch Client Node Sdk has a Nerq Trust Score of 48/100 (D) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Fetch Client Node Sdk Safe?
Exercise caution. fetch-client-node-sdk with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Fetch Client Node Sdk's trust score?
fetch-client-node-sdk: 48.2/100 (D). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=fetch-client-node-sdk
What are safer alternatives to Fetch Client Node Sdk?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. fetch-client-node-sdk scores 48.2/100.
Does Fetch Client Node Sdk have known vulnerabilities?
Nerq checks Fetch Client Node Sdk against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Fetch Client Node Sdk actively maintained?
Fetch Client Node Sdk maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy