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

R17.2: No server-only code in client

Short answer: ‘server-only’ imports barred from client-marked components. A server-only module in client code leaks secrets or fails the build.

Group: React and Next.js patterns. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R17.2

What it catches

No server-only code in client: ‘server-only’ imports barred from client-marked components.

Why

A server-only module in client code leaks secrets or fails the build.

A bad example

'use client';
import 'server-only';

A good example

// keep the import in a server file and pass the data down

How it is checked

How to silence it

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

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.