Methodology
Local, deterministic analysis
All fourteen tools analyse input locally in the browser. There is no backend API for fstab, sshd_config, Compose files, logs or node reports, so nothing sensitive is transmitted. The checks are deterministic functions: the same input always produces the same findings.
Each tool maps its findings to a severity (high, warning, good) and explains the reasoning inline, so an administrator can decide rather than blindly accept an automated verdict.
Sources and attribution
Rules follow official documentation — fstab(5), nfs(5), sshd_config(5), systemd.service, the Compose specification, Docker security best practices and CIS Benchmarks. Where a recommendation is a judgement call (for example MaxAuthTries thresholds), the page says so instead of presenting it as a standard.
References on each tool page link to the primary source. Nothing is copied wholesale; content is summarised with attribution.
Versioning and review
Each tool page shows the analyser version, the review date and the target distributions. A review means the tool logic and documentation were checked for consistency on that date — it does not mean every rule was tested on every distribution.
The rules are intentionally small and auditable. If a rule is ambiguous, the tool favours warning over silence.