brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R5.5: Process & lock safety

Short answer: Every subprocess.run carries timeout=; locks use try/finally. Passing shell=True or an interpolated command string runs a shell that can execute injected input.

Group: Reliability and fallbacks. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R5.5

What it catches

Process & lock safety: every subprocess.run carries timeout=; locks use try/finally.

Why

Passing shell=True or an interpolated command string runs a shell that can execute injected input.

A bad example

subprocess.run(cmd, shell=True)

A good example

subprocess.run(cmd, timeout=60, check=True)

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R5.5 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

What the scanner already leaves alone: Test files and comment lines are not flagged.

A scan reads only the lines you add, so a line that was already in the file is not flagged.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.