FREE1 free audit every month. No card, every finding included.

For apps built with Lovable, Cursor, Bolt or Replit

Find the leaks in your AI-built app
before a stranger does.

Your AI checks what you ask it to. Aster finds what nobody asked for: the open database, the leaked key, the package with a known hole. In plain English, with a fix you approve.

  • Read-only GitHub access
  • 1 free audit every month
  • No card needed

Not ready to connect? See a full sample report first

asterco.app/dashboardEXAMPLE

Repositories

Choose what Aster can read

  • demo/storefrontRead-only
  • demo/marketing-site
  • demo/mobile-app
Run audit

Audit running

Reading demo/storefront

0 of 94 files read · pinned commit a1b2c3d

    Checks

    Running source checks

    • Leaked keys and secrets
    • Supabase and Firebase rules
    • Vulnerable packages
    • Risky code patterns

    Findings · critical first

    3 things to fix, in plain English

    • CRITICAL
      Anyone can read the profiles table: Row Level Security is offsupabase/migrations/0002_profiles.sql · line 3
    • HIGH
      Your OpenAI key ships to the browser via NEXT_PUBLIC_lib/ai.ts · line 4
    • MEDIUM
      Other websites can send requests as your signed-in usersapp/api/route.ts · line 12

    Proposed fix · for your review

    Lock the profiles table

    + alter table profiles enable row level security;+ create policy "own row" on profiles+   using (auth.uid() = id);

    Model: your choice · credit cost shown before generating

    Draft pull request

    Waiting for your review on GitHub

    Turn on Row Level Security for profilesDraft · 1 file added · nothing merges without you
    DRAFT
    Illustration of the Aster workflow with an example repository. Your results will differ. Read a full sample report

    CONNECT GITHUB · CHECK NEXT.JS, REACT, SUPABASE & FIREBASE · FIX WITH THE MODEL YOU CHOOSE

    GitHubJavaScriptTypeScriptReactNext.jsNode.jsSupabaseFirebaseViteExpoPythonRubyGitHub ActionsStripe keys

    Pick from every eligible AI model on OpenRouter to draft your fixes. See every model

    ONE AUDIT

    0files read

    0to review

    Illustration: Aster reads 94 files of an example repository and marks the few that need a closer look.

    WHAT AI TOOLS FORGET

    It works.
    It’s just not locked.

    AI tools build exactly what you ask for. Nobody asks for database rules, a server-only key or a patched Next.js, so they quietly don’t happen. The app runs fine. The door is just open.

    Asking your AI to “check security” helps, but it grades code it just wrote. Aster runs the same 40 checks across your whole repo, every time, before you ship. It finds what’s missing too: a Supabase table anyone can read, a key that ships to every visitor, Firebase rules left in test mode.

    HOW IT WORKS

    Find it. Understand it.
    Fix it. Check it worked.

    1. 01

      Connect a repository

      Pick the repos Aster may read. Access is read-only, and you can revoke it in GitHub any time.

    2. 02

      Read every file

      Up to 1,500 files: code, env files, database rules and package lists. Nothing is installed or run.

    3. 03

      Critical first

      Ranked by real-world impact, each with the file, the line and a plain-English why.

    4. 04

      Draft the fix

      Use Aster Basic for free, or pick a premium model and see its credit cost first.

    5. 05

      Approve, then re-audit

      The fix opens as a draft pull request. You merge it. A fresh audit then tells you if your fix worked.

    THE ASTER SHOW · REAL MISTAKES

    What a scan can’t catch yet,
    our free guides fix.

    Some mistakes a scan can’t catch yet, like fake Stripe payments or admin pages anyone can open. Each free guide shows one in a minute, then gives you the fix and a prompt for your AI. Browse every guide

    YOU STAY IN CONTROL

    A pull request, not a prompt.
    Merged only when you say so.

    Most tools hand you a prompt to paste. Aster drafts the change, shows the cost first, and opens it as a draft pull request or a patch you apply yourself.

    1. 1Read-only by default

      Aster Code AuditGitHub App · every plan
      • ContentsRead
      • MetadataRead
      • Write accessNone

      Repositories: only the ones you select

      Audits read a snapshot. Nothing is written, ever.

    2. 2You approve the fix

      • CRITRLS off: profiles
      • HIGHKey in NEXT_PUBLIC_
      Aster model libraryFree models · 0 credits
      Source & cost confirmed
      Approve & generate

      Pick findings and a model. Premium models show their credit cost first.

    3. 3A draft pull request

      Turn on RLS for profilesaster/fix-profiles-rls → main
      DRAFT
      • BranchNew, created after you confirm
      • MergeYour call
      or download the patch

      Published by Aster Fixes, a separate GitHub authorization. Never merged automatically.

    Illustration with an example repository. Free includes 3 AI fixes a month with Aster Basic; paid plans add premium models.

    WHY IT MATTERS

    5,600 vibe-coded apps scanned.
    400+ leaked secrets found.

    When Escape.tech scanned 5,600 vibe-coded apps, it found more than 2,000 vulnerabilities, 400+ exposed secrets and 175 exposures of personal data.

    Aster checks keys, database rules, packages and risky code. It doesn’t yet check webhooks, admin access or rate limits. Our free guides cover those.

    5,600 VIBE-CODED APPSPUBLISHED RESEARCH
    • Vulnerabilities2,000+
    • Secrets400+
    • Personal data175
    Source: Escape.tech’s scan of 5,600 vibe-coded apps (opens in a new tab), about 4,000 of them built with Lovable. Not Aster data.

    PRICING

    Scan free every month.
    Pay only when you want more.

    Free

    See what’s exposed.

    $0every month

    • 1 audit every month
    • 3 AI fixes / mo with Aster Basic
    • Every check, every finding
    Scan my repo free

    Launch Check

    Before you launch.

    $19once · no subscription

    • 5 audits within 30 days
    • ≈ 75 AI fixes (300 credits)
    • 1 repository
    Get my launch check

    Studio

    For agencies and client work.

    $79/ month

    • 300 audits / month
    • ≈ 500 AI fixes / mo (2,000 credits)
    • 25 repositories
    Start Studio

    Every plan includes every check and every finding — nothing hidden behind a paywall. Monthly prices shown. Fix counts are estimates on standard models. Compare every plan

    Check your repo
    before you hit publish.

    Connect one repo, read what Aster finds, and fix what matters most first. 1 free audit every month, no card needed.

    QUESTIONS

    Before you connect GitHub.
    The questions builders ask.

    I’m not a security person. Is Aster for me?

    Yes, that’s who it’s for. Every finding says what’s wrong, what someone could do with it and what to do next, in plain English. If you can paste a prompt into Cursor or Claude Code, you can act on it.

    Can’t I just ask my AI to check my code?

    You can, and it helps. But your AI checks what you think to ask about, reads the files in front of it and grades code it wrote. It also knows packages only up to its training date. Aster runs the same 40 checks across your whole repo every time, picked from a research library of 293 checks for AI-built apps. It looks for what’s missing, too. No AI reads your code during the audit, so the same code gets the same answer, and a re-audit can show your fix worked. Then fix it with any AI you like.

    Lovable or Supabase already check my app. Why Aster?

    Use both. Built-in checks are a good start. Aster reads your whole repository, whatever tool built it: your code, env files, Supabase migrations, Firebase rules and packages. Then it drafts the fix for you to approve.

    My app is small. Would anyone bother?

    Yes. Bots don’t pick targets by size. They scan public code and websites for keys and open databases automatically, all day.

    Is it safe to give Aster my repository?

    Aster gets read-only access to the repositories you pick. Your code is read in memory, never run, and no source copy is kept. Revoke access in GitHub any time. Where your code goes

    My code isn’t on GitHub. Can I still use Aster?

    Yes. Download your project as a zip from Lovable, Bolt, Replit or your computer, and upload it in your dashboard. Your browser sends only the files Aster checks. The code isn’t stored; only the report is saved. Aster-drafted fixes need GitHub for now.

    What does Aster check?

    Leaked keys from 15+ providers, keys that ship to the browser through NEXT_PUBLIC_ or VITE_, .env files committed to your repo, Supabase tables and storage anyone can read, Firebase rules left open, package versions with known holes (including React2Shell and the Next.js middleware bypass), and risky code like eval, raw SQL and switched-off security checks. Every check and its limits

    What doesn’t it check yet?

    Stripe webhook signatures, login and admin checks on each route, one user reading another user’s data, rate limits and spend caps, and settings made in the Supabase, Firebase or Vercel dashboards. Our free guides cover webhooks, admin checks, reading other users’ data and AI-endpoint limits.

    Does a clean report mean my app is secure?

    No. It means none of Aster’s checks matched. Areas it doesn’t check yet still need your attention, and apps that handle money or sensitive data deserve a specialist review too.

    Will Aster change my code automatically?

    No. You review every fix first. It opens as a draft pull request only after you confirm, and nothing is merged automatically. After you merge, a re-audit shows whether the finding is gone.

    How much does it cost?

    1 audit every month is free, with 3 AI fixes using Aster Basic. Launch Check is $19 once, with no subscription. Pro is $29 a month or $279 a year, and Studio is $79 a month or $759 a year. Compare plans

    Aster

    CHECKING

    YOUR GUIDE TO ASTER

    Hi, I’m Aster.
    Ask me what Aster checks.

    I can’t see your code from here. Please don’t paste secrets or private code.

    Prepared answers are always available.