Jev in production › Code and security review
Semantic linter sends Jev a batched yes/no question per parsed function to flag intent bugs, such as docstring drift or missing auth, that static tools miss.
A semantic linter and language server for the problems deterministic tools cannot see.
nouls splits every file into functions with tree-sitter and asks TypeSafe a batch of yes/no questions about each one. A rule fires when the probability of yes reaches its threshold. Every question is scored independently, so one call per function answers every rule, and unchanged functions are never asked again.
Rule Severity --- --- namebehaviourmismatch warning docstringdrift warning querywithsideeffect warning partialfailure warning checkthenact warning missingauthorisation warning nonidempotentretry error unitmismatch error boundaryerror error misleadingerror info crypticerror info vagueerror info unconstructiveerror info mixedabstraction info
For the project's own README, linking back here: