fleetlint
Policy for a fleet of repositories. fleetlint checks how a repository is set up (hooks, task runner, lint configuration, CI on GitHub, Gitea, Forgejo or GitLab, release pipeline) against a catalog of rules, reports how far it is from compliant, and tells you or your coding agent exactly how to close each gap.
It does not lint code. It checks that the things which lint, test, build and release the code are present, wired together and configured the way you decided they should be, in every repository, the same way.
Install the latest release on Linux or macOS, no package manager needed:
curl --proto '=https' --tlsv1.2 -fsSL https://fleetlint.org/install.sh | sh
Then, in a repository:
fleetlint # zero configuration: discovers the setup, applies the recommended preset
fleetlint fix --apply # writes what can be written; never overwrites a file
The script puts fleetlint into ~/.local/bin after checking the release’s checksum, and its signature when cosign is installed. Homebrew, Scoop, Nix, mise and the container image: see Getting started.
Where to go
| If you want to | Read |
|---|---|
| try it on a repository | Getting started |
| know what it checks and why | The baseline, stack profiles, slop catalog |
| look up a rule | Rule catalog, rule reference, capability matrix |
| configure a repository | Configuration |
| roll it out across a company | Organisations, fleet mode |
| write rules | Writing rules, CEL reference |
| wire it into hooks, CI and editors | Integrations |
| see how it relates to Scorecard, repolinter and alint | Comparison |
| see it running | Demo |
The tool is at github.com/fleetlint/fleetlint, the rules at github.com/fleetlint/catalog. Changes and plans: project.