raiku lint performs static analysis on raiku.toml beyond schema validation, checking for style issues, deprecated fields, and recommended best practices.
Use this file to discover all available pages before exploring further.
raiku lint is an advisory quality checker that goes beyond the hard schema rules enforced by raiku validate. Where raiku validate answers the question “is this package structurally correct?”, raiku lint answers “is this package well-written?”. It inspects raiku.toml, version.yml, and README.md for common problems such as placeholder build commands, overly generic names, missing descriptions or licenses, suspicious version/stability combinations, and thin README content. Lint issues are separated into three levels — error, warning, and info — and printed in a structured table so you can address them in priority order.
A package can pass raiku validate and still have lint issues. Always run raiku lint before opening a PR to ensure your package meets community quality standards.
When lint issues are found, raiku lint prints a table like this:
Level Field Message ──────── ──────────────── ────────────────────────────────────────────────────────── warning description No description provided. Add a short description to ... warning license No license specified. Add an SPDX identifier (MIT, ...). info tags No tags defined. Tags help users find your package via ... info homepage No homepage or repository URL. Consider linking to ... info changelog Changelog only has a generic initial entry. Keep it ... 0 error(s) 3 warning(s) 2 info
When no issues are found, a green panel confirms the clean result:
╭──────────────────────────────────╮│ ✓ No lint issues found. │╰──────────────────────────────────╯
Use raiku lint --strict in CI together with raiku validate --strict to enforce both structural correctness and quality standards on every pull request.