Is Http Safe?

Http — Nerq Trust Score 60.7/100 (C+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-01.

Use Http with some caution. Http is a Node.js package with a Nerq Trust Score of 60.7/100 (C+), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 80/100. Popularity: 52/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Machine-readable data (JSON).

Is Http safe?

CAUTION — Http has a Nerq Trust Score of 60.7/100 (C+). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → {name} Privacy Report →

What is Http's trust score?

Http has a Nerq Trust Score of 60.7/100, earning a C+ grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
80
Popularity
52

What are the key security findings for Http?

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

Security score: 80/100 (strong)
Popularity: 52/100 — community adoption

What is Http and who maintains it?

Authorslandelle
Categorynpm
SourceN/A

Similar Npm by Trust Score

@vitest/spy (70)express (70)react-is (70)yargs-parser (70)@aws-sdk/types (70)
See all safest Npm →

Safety Guide: Http

What is Http?

Http is a Node.js package — Gatling JS is a JavaScript/TypeScript interface for the [Gatling load testing tool](https://gatling.io/)..

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/[email protected]/http

Key Safety Concerns for Node.js packages

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

Trust Assessment

Http has a Nerq Trust Score of 61/100 (C+) 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 safe to use?
Use with some caution. @gatling.io/http has a Nerq Trust Score of 60.7/100 (C+). Strongest signal: security (80/100). Score based on security (80/100), popularity (52/100).
What is Http's trust score?
@gatling.io/http: 60.7/100 (C+). Score based on: security (80/100), popularity (52/100). Scores update as new data becomes available. API: GET nerq.ai/v1/[email protected]/http
What are safer alternatives to Http?
In the npm category, more Node.js packages are being analyzed — check back soon. @gatling.io/http scores 60.7/100.
Does Http have known vulnerabilities?
Nerq checks Http against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 80/100. Run your package manager's audit command for the latest findings.
How actively maintained is Http?
Http has a trust score of 60.7/100 (C+). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

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 Policy