Is Pgdump Toc Rewrite Safe?

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

Pgdump Toc Rewrite 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 Pgdump Toc Rewrite safe?

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

Security Analysis → Pgdump Toc Rewrite Privacy Report →

What is Pgdump Toc Rewrite's trust score?

Pgdump Toc Rewrite 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 Pgdump Toc Rewrite?

Pgdump Toc Rewrite'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 Pgdump Toc Rewrite 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

Pgdump Toc Rewrite vs lrtablePgdump Toc Rewrite vs i-slint-backend-winitPgdump Toc Rewrite vs pgrx-sql-entity-graph

Safety Guide: Pgdump Toc Rewrite

What is Pgdump Toc Rewrite?

Pgdump Toc Rewrite is a Rust crate — Command-line utility and a library that can be used to rewrite Babelfish logical DB name in pg_dump TOC and Babelfish catalog files.

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=pgdump_toc_rewrite

Key Safety Concerns for Rust crate

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

Measured Signals

Pgdump Toc Rewrite 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 Pgdump Toc Rewrite Safe?
pgdump_toc_rewrite 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 Pgdump Toc Rewrite's trust score?
pgdump_toc_rewrite: 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=pgdump_toc_rewrite
What are safer alternatives to Pgdump Toc Rewrite?
In the Rust Crates category, more Rust crates are being analyzed — check back soon. pgdump_toc_rewrite scores 48.2/100.
Does Pgdump Toc Rewrite have known vulnerabilities?
Nerq checks Pgdump Toc Rewrite 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 Pgdump Toc Rewrite use unsafe code?
Check Pgdump Toc Rewrite'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