Is Http Request Context Safe?

Http Request Context — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-06-06.

Exercise caution with Http Request Context. Http Request Context 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 Http Request Context safe?

NO — USE WITH CAUTION — Http Request Context 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 → Http Request Context Privacy Report →

What is Http Request Context's trust score?

Http Request Context 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 Http Request Context?

Http Request Context'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 Request Context and who maintains it?

Authorzhujun24
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

rn-dropdown-select (58)evo-shadcn-ui-default-theme-lib (58)hit-canvas (58)@betterdb/agent (58)@agenttoll/sdk (58)
See all safest Npm →

Compare

Http Request Context vs rn-dropdown-selectHttp Request Context vs evo-shadcn-ui-default-theme-libHttp Request Context vs hit-canvas

Safety Guide: Http Request Context

What is Http Request Context?

Http Request Context is a Node.js package — Store context in http middleware lifecycle..

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-request-context

Key Safety Concerns for Node.js package

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

Trust Assessment

Http Request Context 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 Http Request Context Safe?
Exercise caution. http-request-context 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 Http Request Context's trust score?
http-request-context: 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=http-request-context
What are safer alternatives to Http Request Context?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. http-request-context scores 48.2/100.
Does Http Request Context have known vulnerabilities?
Nerq checks Http Request Context 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 Request Context actively maintained?
Http Request Context 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