cargo-diagnostics@1.6.1
VERIFIEDPublisher claims: "Finds out why a Cargo run, batch or play went wrong or cost too much, after the fact: traces one run step by step, draws the path it took with the failing step marked, groups a batch's errors by root cause, and attributes credit spend to each step and provider. Triggers: "why did this fail", "it succeeded but the output is wrong", "half my rows are empty", "why is this column blank", "what broke in this batch", "why did that cost so much", "which node is burning credits", "it worked yesterday", "these results look wrong", "it went down the wrong path", "this step never ran", "show me what the run did". Skip when: setting up an alert for next time, use cargo-observability; just downloading the data, use cargo-analytics." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-11-04 and scored it 88/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.