Is Cu Bincode Derive Safe?

Cu Bincode Derive — Nerq Trust Score 57.2/100 (C grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-03-30.

Use Cu Bincode Derive with some caution. Cu Bincode Derive is a Rust crate with a Nerq Trust Score of 57.2/100 (C), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 60/100. Data sourced from crates.io registry, GitHub, NVD, and RustSec advisory database. Last updated: 2026-03-30. Machine-readable data (JSON).

Is Cu Bincode Derive safe?

CAUTION — Cu Bincode Derive has a Nerq Trust Score of 57.2/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 Cu Bincode Derive's trust score?

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

Security
90
Popularity
60

What are the key security findings for Cu Bincode Derive?

Cu Bincode Derive'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: 60/100 — community adoption

What is Cu Bincode Derive and who maintains it?

AuthorUnknown
Categorycrates
SourceN/A

Similar Crates by Trust Score

glob (63)bincode_derive (63)arboard (63)libbz2-rs-sys (63)bitflags (63)
See all safest Crates →

Safety Guide: Cu Bincode Derive

What is Cu Bincode Derive?

Cu Bincode Derive is a Rust crate — Implementation of #[derive(Encode, Decode)] for bincode.

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=cu-bincode-derive

Key Safety Concerns for Rust crates

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

Trust Assessment

Cu Bincode Derive has a Nerq Trust Score of 57/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 Cu Bincode Derive safe to use?
Use with some caution. cu-bincode-derive has a Nerq Trust Score of 57.2/100 (C). Strongest signal: security (90/100). Score based on security (90/100), popularity (60/100).
What is Cu Bincode Derive's trust score?
cu-bincode-derive: 57.2/100 (C). Score based on: security (90/100), popularity (60/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=cu-bincode-derive
What are safer alternatives to Cu Bincode Derive?
In the crates category, more Rust crates are being analyzed — check back soon. cu-bincode-derive scores 57.2/100.
Does Cu Bincode Derive have known vulnerabilities?
Nerq checks Cu Bincode Derive 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 Cu Bincode Derive use unsafe code?
Check Cu Bincode Derive's crate documentation for unsafe code usage. Trust score: 57.2/100. Fewer unsafe blocks generally indicates better memory safety.
API: /v1/preflight Trust Badge API Docs

Browse Categories

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.