Aster does
- Read only the repositories you choose
- Read one version of your code, in memory
- Explain each finding in plain English, with the file and line
- Show the most a fix can cost before it runs
- Re-audit, so you can see a fix worked
HOW IT WORKS
Connect GitHub read-only and see what’s open, critical first, in plain English. Approve the fixes you want, then a re-audit shows they worked. 1 free audit every month, no card.
THE JOURNEY
Steps 1 to 5 are your free audit, every month. Free also includes 3 AI fixes a month with Aster Basic, and paid plans add premium models. Nothing reaches your repo until you confirm it.
Install the Aster Code Audit App. It can only read: Contents: read and Metadata: read. It has no write access.
You pick which repos Aster can see, and only those show up. Revoke access in GitHub whenever you like.
Aster reads one version of your code, up to 1,500 files, in memory. That includes code, env files, Supabase migrations, Firebase rules and lockfiles. Nothing is installed or run.
What is read, exactlyKeys anyone can copy from your site (secrets behind NEXT_PUBLIC_). Tables anyone can read (Row Level Security off). Firebase rules left in test mode, package versions with known holes (like React2Shell) and risky code. You can close the tab while it runs.
Critical first, then high, medium and low. Each finding names the file and line, says why it matters and suggests a next step. Every finding is free, on every plan.
Anatomy of a findingUse Aster Basic for free, or pick another model on a paid plan. You see the most it can cost before anything runs. Your code goes only to the provider you pick.
See every modelAster drafts a small, focused change. You read every changed line and its check results. Then you decide.
A second app, Aster Fixes, publishes it. You authorize it separately. It opens a draft for you to review.
You merge on GitHub. A fresh audit checks the new code against the last report. When the finding is gone, it tells you plainly: your fix worked.
Step demos are illustrations with an example repository. Your results will differ.
ANATOMY OF A FINDING
supabase/migrations/0002_profiles.sql · line 3
3 create table profiles (id uuid primary key, email text);4 -- no "enable row level security" for this table
Row Level Security (RLS) is never turned on. Anyone with your public key can read every row.
Turn on RLS and add a policy so each user reads only their own row.
Critical, high, medium or low tells you where to start. It’s a priority, not proof: Aster doesn’t try to break in.
The exact spot in the version Aster read, so you can jump straight to it in your editor.
The lines that matched, in context. Anything that looks like a secret is blanked out.
One plain sentence about the problem. It’s written for the person who has to fix it, not a security team.
A suggested fix. Turn it into a drafted change to review, with Aster Basic or the model you choose.
CLEAR BOUNDARIES
Aster never merges automatically.See the approval flow
Permissions, retention and limits in full: Trust & scope
QUESTIONS
Yes. Connect GitHub, pick the repos you share with the Aster App, and run a read-only audit. Free includes 1 audit and 3 AI fixes with Aster Basic every month. Paid plans add more audits and premium models.
That’s who it’s for. Each finding says what’s wrong in plain English, with the file and line. Aster drafts the fix for you to approve. Some steps, like replacing a leaked key, still need a click in your dashboard, and Aster tells you which.
No. You can leave the dashboard while an audit runs and come back to its progress or the saved report.
You can, and it helps. But your AI checks what you ask, sees only the files in front of it, and knows packages only up to its training date. Aster runs the same 40 checks on your whole repo, every time. Same code, same answer, so a re-audit shows your fix worked.
No. The audit app can only read. To publish a fix, you authorize Aster Fixes on the repos you pick and confirm the change. It opens a draft pull request on a new branch, and you decide whether to merge.
No. It means none of Aster’s checks matched. It doesn’t check webhook signatures, login and admin checks on each route, one user reading another’s data, rate limits or dashboard settings yet. Our free guides cover those.
1 audit every month is free. Launch Check is $19 once, with no subscription. Pro is $29 a month or $279 a year. Studio is $79 a month or $759 a year. Compare plans
Connect GitHub, pick a repo, and read what comes back in plain English. Read-only access, no card needed.