Architecture

GitHub-native. Five-minute install. No workflow change.

  1. 01

    Install the GitHub App on your Lovable repo

    Quenchloop requests read-only access to code, pull requests, and metadata. Write access is scoped to checks and the isolated branches Quenchloop creates for fix PRs.

  2. 02

    Lovable commits trigger an analysis automatically

    Quenchloop identifies commits authored by the Lovable bot and ignores the rest by default. An isolated Modal sandbox clones the repo, runs static + LLM analysis, and destroys itself within five minutes.

  3. 03

    You receive a single PR comment with findings

    No dashboard to check. The comment includes severity-sorted findings, file:line references, an estimated credit cost, and a one-click link to generate the fix.

  4. 04

    Quenchloop opens a PR against a new branch

    Mechanical fixes are applied via AST transformations. Tests for critical paths are generated. Ambiguous logic fixes are reviewed by you before merge. Quenchloop never pushes to your default branch.

Detection catalog

12 Lovable-specific patterns, out of the box.

CategoryPatternSeverityFix cost
lovablesupabase.auth.onAuthStateChange callback awaits Supabase directlyhigh~90
lovableProtectedRoute checks session without a loading statemedium~70
lovableSecret-looking env var uses VITE_ prefix — exposed in client bundlehigh~100
lovableSupabase table with user_id missing or bypassing RLScritical~120
lovableThird-party API key sent from the browser to a non-Supabase hostcritical~150
lovableEdge function directory has no matching block in config.tomlhigh~60
lovableGenerated Supabase types.ts out of sync with migration SQLmedium~35
lovablePostgres SECURITY DEFINER function without SET search_pathhigh~12
productionconsole.log statements left in codelow~5
typesExcessive use of `any` or `unknown` castsmedium~25
productionHardcoded API keys in sourcecritical~200
performanceImage rendered without width/height/loading attrslow~10
How it works — Quenchloop