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

R2.3: Dual-key entity resolution

Short answer: Discriminate UUID/CUID vs domain/slug before database query. An id that is a UUID in one place and a slug in another is looked up in the wrong column.

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

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R2.3

What it catches

Dual-key entity resolution: discriminate UUID/CUID vs domain/slug before database query.

Why

An id that is a UUID in one place and a slug in another is looked up in the wrong column.

A bad example

findOne({ id: param })

A good example

const where = isUuid(param) ? { id: param } : { slug: param };
findOne(where)

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R2.3 -- 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.

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.