Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Package.json avoids ‘*’ or unbounded range dependencies. A wildcard version takes whatever was published last, including a bad release.
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.2
No wildcard dependency versions: package.json avoids ‘*’ or unbounded range dependencies.
A wildcard version takes whatever was published last, including a bad release.
"left-pad": "*"
"left-pad": "1.3.0"
brevio-core scan: a scan of added lines (code_rules.scan_added_lines_for_rules).A person can silence one finding with brevio-core: ignore R16.2 -- 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: Only package.json is checked, and the top-level version and private fields 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.