Few things you wanted to know about how OVYERO works, where your code goes, and what happens when a rule is wrong.
Verdicts come back in about a second. Most engineers don't notice it ran. They only notice when something needs fixing.
Mostly rule-based — pattern matching, AST analysis, and schema validation. A few checks use an LLM as a judge (clearly labeled). Rule-based checks return the same result for the same input, every time.
Files are evaluated locally by the hook. Only verdict metadata (rule ID, file path, severity) is sent to the dashboard. Source never leaves your machine.
Not yet. The rule set is curated and maintained by us. Custom rule authoring is on the roadmap. For now, you tune which domains run via your project type.
Language-agnostic where rules are pattern- or AST-based, so it works on any text-based source. Some domains are language-specific, most apply broadly.
There's a bypass flag for genuine emergencies, and every use of it is recorded in the audit log. No silent skips. You can always see what was overridden and by whom.
We want to make Ovyero the best it can be and input from you genuinely helps.
ezra@visnryentertainment.com