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

R10.1: Explicit HTTP request timeouts

Short answer: Every fetch/axios call specifies timeout or AbortSignal. A request with no timeout can hang a worker for ever.

Group: API and network robustness. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R10.1

What it catches

Explicit HTTP request timeouts: every fetch/axios call specifies timeout or AbortSignal.

Why

A request with no timeout can hang a worker for ever.

A bad example

response = requests.get(url)

A good example

response = requests.get(url, timeout=10)

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R10.1 -- 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 calls that pass timeout= on the same line 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.