Is Http Body Safe?

Http Body — Nerq Trust Score 63.2/100 (C+ grade). Score based on 2 independent trust signals. Last analyzed: 2026-04-12

Http Body is a Rust crate with a Nerq Trust Score of 63.2/100 (C+), based on 3 independent data dimensions. Last analyzed: 2026-04-12 Security: 90/100. Popularity: 100/100. Data sourced from crates.io registry, GitHub, NVD, and RustSec advisory database. Last updated: 2026-04-12. Machine-readable data (JSON).

Is Http Body safe?

Trust Score Breakdown — Http Body has a Nerq Trust Score of 63.2/100 (C+). Measured across 2 independent trust signals (as of 2026-04-12).

Security Analysis → Http Body Privacy Report →

What is Http Body's trust score?

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

Security
90
Popularity
100

What are the key security findings for Http Body?

Http Body's strongest signal is popularity at 100/100. No known vulnerabilities have been detected.

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

What is Http Body and who maintains it?

AuthorUnknown
CategoryRust Crates
SourceN/A

Http Body Across Platforms

Same developer/company in other registries:

http-body
62/100 · npm

Similar Crates by Trust Score

indexmap (63)crypto-common (63)darling_core (63)windows-core (63)oorandom (63)
See all safest Crates →

Compare

Http Body vs indexmapHttp Body vs crypto-commonHttp Body vs darling_core

Safety Guide: Http Body

What is Http Body?

Http Body is a Rust crate — Trait representing an asynchronous, streaming, HTTP request or response body. .

How to Verify Safety

Run cargo audit. Review on crates.io for activity.

You can also check the trust score via API: GET /v1/preflight?target=http-body

Key Safety Concerns for Rust crate

When evaluating any Rust crate, watch for: dependency vulnerabilities, unsafe code, maintenance status.

Measured Signals

Http Body has a Nerq Trust Score of 63/100 (C+). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance50/100
Popularity100/100
Quality40/100
Community35/100

Based on 5 dimensions. Data from crates.io registry, GitHub, NVD, and RustSec advisory database.

What data does Http Body collect?

Http Body is a Rust crate maintained by Unknown. It receives approximately 519,515,276 weekly downloads.

As a development package, Http Body does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Http Body Privacy Report · Privacy review

Is Http Body secure?

Security score: 90/100. Http Body has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

License information not available. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Http Body Security Report

Http Body Across Platforms

Same developer/company in other registries:

http-body (npm, 62/100)

How we calculated this score

Http Body's trust score of 63.2/100 (C+) is computed from crates.io registry, GitHub, NVD, and RustSec advisory database. The score reflects 5 independent dimensions: security (90/100), maintenance (50/100), popularity (100/100), quality (40/100), community (35/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

Signals last measured on April 12, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Http Body Safe?
http-body with a Nerq Trust Score of 63.2/100 (C+). Strongest signal: popularity (100/100). Score based on Security (90/100), Popularity (100/100).
What is Http Body's trust score?
http-body: 63.2/100 (C+). Score based on Security (90/100), Popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=http-body
What are safer alternatives to Http Body?
In the Rust Crates category, more Rust crates are being analyzed — check back soon. http-body scores 63.2/100.
Does Http Body have known vulnerabilities?
Nerq checks Http Body 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.
Does Http Body use unsafe code?
Check Http Body's crate documentation for unsafe code usage. Trust score: 63.2/100. Fewer unsafe blocks generally indicates better memory safety.
API: /v1/preflight Trust Badge API Docs

Browse Categories

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy