alint
A general repository linter that lets teams declaratively define rules and conventions for their repos beyond what language-specific linters cover, including checks for directory structure, required files, file staleness/freshness, file size, binary files, and invisible Unicode, all checked deterministically. It packages the hand-authored scripts large repos typically use for these checks into a fast, reusable, and extensible tool.
What it addresses
Many large repositories rely on hand-authored scripts to enforce conventions (directory structure, required files, file freshness, etc.) that language-specific linters don't cover.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
alint
A general repository linter that lets teams declaratively define rules and conventions for their repos beyond what language-specific linters cover, including checks for directory structure, required files, file staleness/freshness, file size, binary files, and invisible Unicode, all checked deterministically. It packages the hand-authored scripts large repos typically use for these checks into a fast, reusable, and extensible tool.
Problem: Many large repositories rely on hand-authored scripts to enforce conventions (directory structure, required files, file freshness, etc.) that language-specific linters don't cover.
Posted by @aleqs · Original comment ↗
“I've been working on a general repository linter. The idea is to declaratively define a set of rules/conventions for your repo, (for things that language-specific linters don't cover), covering things from directory structure, required files, file staleness/freshness, file size, rules for binary files, rules around use of invisible Unicode, etc. - which can be checked deterministically.”