The Hermes Labs open-source tools catalog.
The Hermes Labs public catalog is a workflow, not a wall of repositories: begin with a project-local setup, inspect language and input data before runtime, observe and guard live behavior, evaluate changes, and preserve the context behind decisions. Each tool below names the boundary of what its present evidence supports.
Follow the path: start → static checks → runtime → evaluate → memory
See also: research and evidence · upstream contributions
Try a real LintLang scan in your browser →
Evaluating these controls for production? Discuss adoption and evidence boundaries →
Curated public catalog
How to read this catalog
Inspect the evidence
A public repository is an inspectable artifact, not a claim of production fitness. Read its README, limitations, tests, and release history against your actual environment before adoption.
Separate kinds of proof
Local tests, a public package, a benchmark, and independent evaluation answer different questions. The boundary on each tool names material work that remains before a stronger claim is fair.
Use the research as context
The research index provides the conceptual and empirical work behind Hermes Labs. It informs the engineering program; it does not certify every tool or deployment.
To reproduce a boundary, report a false positive, or improve an adapter, open an issue in the relevant project repository.
The wider organization remains available for historical and secondary source inspection. Those repositories are not part of this curated catalog. Browse the full GitHub organization