Akimiya-z/codex-guard
C3Quality gate for AI/Codex-generated pull requests: blocks TODO leftovers, leaked secrets, sloppy commits and red CI before they reach main.
★ 100+ · Akimiya-z/codex-guard source on GitHub · this plugin in the registry
Akimiya-z/codex-guard is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, eval in build output only, decodes base64 payloads.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×9 in authored code, e.g. dsh/index.js:2, dsh/index.js:2 |
| eval in build output only | eval_bundled | ×1 in build output only, e.g. dist/index.js:5 |
| decodes base64 payloads | base64_decode | ×1 in authored code, e.g. src/config.js:94 |
| reads credential-class env vars | token_env | GITHUB_TOKEN |
Services it injects
tools
Outbound domains
docs.github.com api.github.com uploads.github.com
Environment variables it reads
GITHUB_EVENT_PATH GITHUB_REPOSITORY NODE_DEBUG NODE_V8_COVERAGE GITHUB_TOKEN GITHUB_EVENT_NAME GITHUB_SHA GITHUB_REF GITHUB_WORKFLOW GITHUB_ACTION
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.