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

R16.7: Single package manager

Short answer: Repo roots maintain exactly one package manager lockfile. Two lockfiles mean two sets of versions, and nobody knows which is real.

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

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R16.7

What it catches

Single package manager: repo roots maintain exactly one package manager lockfile.

Why

Two lockfiles mean two sets of versions, and nobody knows which is real.

A bad example

package-lock.json and pnpm-lock.yaml

A good example

pnpm-lock.yaml only

How it is checked

How to silence it

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