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

R9.1: No untyped escape hatches

Short answer: No as any casts or z.any() schemas in production source. any turns the type checker off for everything it touches.

Group: Type safety. Status: stable. Generated from the rule definitions; do not edit by hand.

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

What it catches

No untyped escape hatches: no as any casts or z.any() schemas in production source.

Why

any turns the type checker off for everything it touches.

A bad example

const user = (await res.json()) as any;

A good example

const user = UserSchema.parse(await res.json());

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R9.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, test helpers and setup 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.