Content

Rule kinds in the Content family. Each entry below has its own page with options, an example, and any auto-fix support.

• file_content_matches — File contents must contain at least one match for a regex.
• file_content_forbidden — File contents must NOT match a regex.
• file_header — The first N lines must match a regex (line-oriented).
• file_starts_with — Byte-level prefix / suffix check.
• file_ends_with — Byte-level prefix / suffix check.
• file_hash — Content SHA-256 must equal the expected digest.
• file_max_size — File must be at most max_bytes in size.
• file_min_size — File must be at least min_bytes in size.
• file_min_lines — File must have at least min_lines lines (\n-terminated, with an unterminated trailing segment counting as one more — wc -l semantics).
• file_max_lines — File must have at most max_lines lines, using the same accounting as file_min_lines.
• file_footer — Last lines lines of each file in scope must match a regex.
• file_shebang — First line of each file in scope must match the shebang regex.
• file_is_text — Content is detected as text (magic bytes + UTF-8 validity check) — fails on binary files matched by paths.
• file_is_ascii — Every byte in the file must be < 0x80.