Inspection pipeline | Status logic | Evidence used by the rules | Current rule behavior | How legend clarity is interpreted | Why some rules return INFO | Practical interpretation

Programmatic rule registry

Install from CRAN | Development version | Check your installation | Development setup

Basic workflow | What the report contains | Manual analysis | Render an HTML report | How to read statuses

Completeness | Rule 1: Clear title | Rule 2: Axis labels | Rule 3: Missing values and gaps | Rule 4: Legend clarity | Rule 5: Source and context | Rule 6: Annotation for key message | Readability | Rule 7: Readable text | Rule 8: Accessible color choices | Rule 9: Avoid clutter | Rule 10: Grid and guide balance | Rule 11: Consistent formatting | Rule 12: Appropriate chart type | Rule 13: Readable scale labels | Rule 14: Overplotting management | Rule 15: Direct labeling when useful | Rule 16: Visual hierarchy | Integrity | Rule 17: Truthful scale | Rule 18: No distorted baseline | Rule 19: Avoid misleading encodings | Rule 20: Handle outliers honestly | Rule 21: Proportional areas | Rule 22: Uncertainty when needed | Rule 23: Avoid cherry picking | Rule 24: Respect data granularity | Rule 25: Neutral framing