Is Http Client Wrapper Safe?

Http Client Wrapper — Nerq Trust Score 46.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-27.

Exercise caution with Http Client Wrapper. Http Client Wrapper is a npm package with a Nerq Trust Score of 46.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 Http Client Wrapper safe?

NO — USE WITH CAUTION — Http Client Wrapper has a Nerq Trust Score of 46.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 → Http Client Wrapper Privacy Report →

What is Http Client Wrapper's trust score?

Http Client Wrapper has a Nerq Trust Score of 46.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 Http Client Wrapper?

Http Client Wrapper'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 Http Client Wrapper and who maintains it?

Authora1im
Categorynpm Packages
SourceN/A

Http Client Wrapper Across Platforms

Same developer/company in other registries:

Http.Client.Wrapper
46/100 · nuget

Similar Npm by Trust Score

create-sss (56)sysdb (56)better-auth-lead (56)@typeserve/core (56)happy-translate (56)
See all safest Npm →

Compare

Http Client Wrapper vs create-sssHttp Client Wrapper vs sysdbHttp Client Wrapper vs better-auth-lead

Safety Guide: Http Client Wrapper

What is Http Client Wrapper?

Http Client Wrapper is a Node.js package — Http client wrapper.

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=http-client-wrapper

Key Safety Concerns for Node.js package

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

Trust Assessment

Http Client Wrapper has a Nerq Trust Score of 46/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 Http Client Wrapper Safe?
Exercise caution. http-client-wrapper with a Nerq Trust Score of 46.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Http Client Wrapper's trust score?
http-client-wrapper: 46.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=http-client-wrapper
What are safer alternatives to Http Client Wrapper?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. http-client-wrapper scores 46.2/100.
Does Http Client Wrapper have known vulnerabilities?
Nerq checks Http Client Wrapper 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 Http Client Wrapper actively maintained?
Http Client Wrapper 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