The Destructive Command Guard (dcg) is for blocking dangerous git and shell commands from being executed by agents.
This week focused on hardening the core detection logic that guards against destructive shell commands. The team fixed multiple parsing gaps where dangerous commands—particularly git operations, filesystem mutations, and heredoc injections—were evading judgment due to quoting, wrapping, or recursive…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in destructive_command_guard's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
fix(bridges): the OpenCode plugin loads on OpenCode 1.3.4+, the Cursor bridges fail closed, Cursor's Shell tool is judged (GH #516, #517, #518)
test(history): stamp the #513 analysis rows a minute back; same-millisecond rows were not counted
feat(git): report merge-checked `git branch -d` as core.git:branch-delete, keep old entries covering it (GH #509)
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.