Is Pezkuwi Availability Distribution Safe?

Pezkuwi Availability Distribution — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Pezkuwi Availability Distribution is a Rust crate with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 Security: 90/100. Popularity: 0/100. Data sourced from crates.io registry, GitHub, NVD, and RustSec advisory database. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Pezkuwi Availability Distribution safe?

Trust Score Breakdown — Pezkuwi Availability Distribution has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Pezkuwi Availability Distribution Privacy Report →

What is Pezkuwi Availability Distribution's trust score?

Pezkuwi Availability Distribution 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 Pezkuwi Availability Distribution?

Pezkuwi Availability Distribution's strongest signal is security at 90/100. No known vulnerabilities have been detected.

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

What is Pezkuwi Availability Distribution and who maintains it?

AuthorUnknown
CategoryRust Crates
SourceN/A

Similar Crates by Trust Score

lrtable (58)i-slint-backend-winit (58)pgrx-sql-entity-graph (58)myutil (58)rlua (58)
See all safest Crates →

Compare

Pezkuwi Availability Distribution vs lrtablePezkuwi Availability Distribution vs i-slint-backend-winitPezkuwi Availability Distribution vs pgrx-sql-entity-graph

Safety Guide: Pezkuwi Availability Distribution

What is Pezkuwi Availability Distribution?

Pezkuwi Availability Distribution is a Rust crate — The Availability Distribution subsystem. Requests the required availability data. Also distributes availability data and chunks to requesters..

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=pezkuwi-availability-distribution

Key Safety Concerns for Rust crate

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

Measured Signals

Pezkuwi Availability Distribution has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Pezkuwi Availability Distribution Safe?
pezkuwi-availability-distribution 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 Pezkuwi Availability Distribution's trust score?
pezkuwi-availability-distribution: 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=pezkuwi-availability-distribution
What are safer alternatives to Pezkuwi Availability Distribution?
In the Rust Crates category, more Rust crates are being analyzed — check back soon. pezkuwi-availability-distribution scores 48.2/100.
Does Pezkuwi Availability Distribution have known vulnerabilities?
Nerq checks Pezkuwi Availability Distribution 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 Pezkuwi Availability Distribution use unsafe code?
Check Pezkuwi Availability Distribution's crate documentation for unsafe code usage. Trust score: 48.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