Dicklesworthstone/destructive_command_guard

The Destructive Command Guard (dcg) is for blocking dangerous git and shell commands from being executed by agents.

5,180
Stars
7 months
Age
0
Published reviews
0
Questions

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-07-19).

Continuity30% of headline59

Activity on 57 of 90 tracked days in the last 90 and 22 of 30 in the last 30.

Closure30% of headline50

Merged 8 of 40 PRs opened and closed 66 of 75 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.

Shipping20% of headline100

21 releases in the last 180 days, 18 in the last 90 and 7 in the last 30 — a steady cadence scores highest.

Liveness10% of headline100

Last push 0 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).

Support burden10% of headline99

2 open issues against 5,180 stars — about 0 open issues per 1,000 stars. Lighter backlogs score higher.

Adoption confidence100

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality73

Modeled from PR/issue responsiveness and upkeep signals. Activity pulse

Risk score18

Modeled — lower is better; adoption and continuity risk. Repository

Stays active (30d)73%

Modeled chance the repo stays active over 30 days. Activity pulse

Stays active (90d)74%

Modeled chance the repo stays active over 90 days. Activity pulse

Release rhythm (180d)100

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)41%

Modeled — lower is better; concentration of commits in few maintainers. Contributors graph

Join the conversation

Reviews · Questions · Posts

Share what you know about destructive_command_guard — write a review from your real experience, ask an implementation question, or publish a post about how you use it.

Share your experience

Write or update your review

Explain what worked, what broke down, and what another team should know before adopting destructive_command_guard.

Write your review now — it saves locally and publishes automatically after you sign in.

Rating
Positive attributes
Negative attributes

Project Q&A

Questions and answers

Browse implementation threads tied directly to Dicklesworthstone/destructive_command_guard. Each question links through to the full answer page.

Q&A No threads yet

Be the first to ask how teams run destructive_command_guard in production. Every question you post becomes a durable, searchable answer page other developers can find.

Ask the first question

Related posts

Posts tagged with the same topics

These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.

Posts No topic-linked posts yet

Share how your team uses destructive_command_guard — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.

Write the first post
Get a weekly email with the hottest new projects in the Programming Languages and Rust world.
No Spam. Unsubscribe easily at any time.

Copyright 2018-2026 Awesome Open Source.  All rights reserved.