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

R15.4: Image broken state fallback

Short answer: Img / Image tags provide alt and error state fallback. A broken image with no fallback leaves a hole in the layout.

Group: Error boundaries and fallback rendering. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R15.4

What it catches

Image broken state fallback: img / Image tags provide alt and error state fallback.

Why

A broken image with no fallback leaves a hole in the layout.

A bad example

<img src={url} alt="" />

A good example

<img src={url} alt="Team photo" onError={useFallback} />

How it is checked

How to silence it

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