Home

diagprint turns failures into actionable, structured diagnostics. Define a diagnostic once, then carry it safely through terminal output, compiler tooling, editors, CI, code scanning, guarded remediation, verification, telemetry and privacy-aware reporting.

Important

The core rule: diagnostics may explain and propose. Mutation must be explicit, structured, validated, and reject uncertainty.

⚡ Start here

Page	What's there
📥 Installation	Add the crate, install the CLI, pick features
🚀 Quick Start	A reporter and your first diagnostic
⌨️ CLI Reference	scan, history, why, timeline, blame, graph, replay, capsule
🧪 Examples	Runnable cargo run --example … by topic

🧭 Explore

Build	Ship	Fix	Investigate
🎯 Diagnostics & Sources	🖨️ Rendering & Output	🔧 Remediation	🔬 Diagnostic Forensics
🌉 Ecosystem Interop	🚦 CI & Code Scanning	🛡️ Safety Model	🧾 Schemas & Specs
📦 Features & Crates	🎨 Themes & Documentation	🛠️ Contributing	🗺️ Roadmap & Releases

🩺 What it does

• 🖥️ Rendering: rich terminal output with primary and secondary labels; JSON, Markdown, plain, compiler-style, HTML, GitHub Actions and SARIF.
• 🧾 Sources: virtual and in-memory sources, immutable snapshots, per-source revisions, stale-source detection, captured diagnostics.
• 🔧 Remediation: guarded fixes, transactional multi-file FixPlans, post-fix verification.
• 🚦 CI & reporting: canonical fingerprints and report digests, semantic deltas, baseline-aware CI, artifact receipts, capsules, project scanning.
• 🔬 Forensics: hash-chained diagnostic history, case files (why), timelines, Git provenance (blame), relationship graphs and remediation replay.
• 🌉 Interop: anyhow, tracing, miette, codespan, Ariadne, annotate-snippets, rustc and Cargo ingestion, plus a bridge SDK.

🔗 Links

🌐 Project site & live demo · 📖 API docs · 📦 crates.io · 📝 Changelog · 💬 Discord