Aster Code Audit
Needed to run an audit
- Can: Contents: read
- Can: Metadata: read
- Cannot: Write to your code
- Cannot: Open pull requests
- Cannot: Merge changes
Aster only sees repos you shared with the App and can open yourself.
TRUST & SCOPE
Aster gets read-only access to the repos you pick. It never runs your code or saves a copy of your repo, and no AI reads it during an audit. Revoke access any time.
Repositories: only the ones you select
WHERE YOUR CODE GOES
Audits never send your code to an AI model. Your code goes to a model only when you ask for a fix and confirm it.
EVERY PLANSource audit
No AI modelNothing runNo copy of your repo kept
WHEN YOU ASKFix request
You confirm what’s sentYou confirm before publishingYou do the merge
PERMISSIONS
An audit only needs to read. Publishing a fix uses a second app, which you turn on separately for the repos you pick.
Needed to run an audit
Aster only sees repos you shared with the App and can open yourself.
Only if you want to publish a fix
Review or revoke either connection on GitHub at any time.
Who decides what. Every write needs your yes.See the approval flow
The audit app reads one version of your code. It has no permission to write.
Pick the findings and a model. You see the files and the credit cost before anything is sent.
Publish a draft pull request on a new branch with Aster Fixes, or download the patch. Merging stays with you, on GitHub.
Your GitHub sign-in lasts up to eight hours. It lives in a Secure, HttpOnly cookie, and tokens never reach page scripts or localStorage.
An encrypted credential on our server lets an audit finish after you leave. It’s cleared when the job ends, fails, is stopped or expires.
Stop an audit or disconnect GitHub in the dashboard. To remove access fully, revoke or uninstall the App in GitHub settings.
WHAT IS READ
Aster reads the latest commit on your default branch, not your Git history. It downloads it as one archive and keeps the files it checks in server memory. Your report lists what was checked and what was skipped.
SKIPPED AND LISTED IN THE REPORT
WHAT IS CHECKED
Aster reads what your app is made of: code, env files, database migrations, security rules and lockfiles. Unlike a chat with your AI, the same checks run on every file, every time. Each card says what you’re protected from, what Aster looks for, and its limit.
Someone could copy a key from your site or code and run up your bill. Aster finds keys from 15+ providers (Stripe, OpenAI, Anthropic, AWS, Supabase, GitHub and more). It flags secrets behind browser-public prefixes like NEXT_PUBLIC_, VITE_ and EXPO_PUBLIC_. It also flags committed .env files, a missing .gitignore rule and keys in Expo app config. Keys meant to be public are left alone, and matched values are redacted.
LimitAster can’t tell whether a matched key still works.
Someone could slip their own code or database queries into your app. Aster flags eval and other dynamic code, and raw SQL built from user input. It also flags disabled TLS checks, CORS that sends cookies to any site, and login tokens anyone could forge (unsigned JWTs). Plus unsanitized HTML and ignored TypeScript build errors.
LimitWorth a review, not proof. Aster doesn’t run your code or try to break in.
Code meant for your server could ship to every visitor’s browser. Aster flags server-only code pulled into a “use client” file, following relative imports. It also checks JavaScript, JSX, TypeScript and TSX syntax.
LimitAster doesn’t follow package aliases, dynamic imports or bundler transforms.
Anyone with your public key could read or change your users’ data. Aster replays your Supabase migrations in order. It flags tables with Row Level Security off, and policies that let everyone in or any signed-in user. It also flags roles read from user_metadata and public storage buckets. In Firebase, it flags Firestore, Storage and Realtime Database rules left open, in test mode or open to any signed-in user.
LimitOnly what’s in your repo. Aster can’t see settings changed in the Supabase or Firebase dashboard.
Someone could use a publicly known hole in a package your app depends on. Aster checks your Next.js and React versions for React2Shell and the Next.js middleware bypass. It checks every package in your lockfile against known advisories from OSV.dev.
LimitOnly package names and versions go to OSV.dev. Aster doesn’t test whether your code uses the vulnerable part.
These matter, but Aster doesn’t check them yet: Stripe webhook signatures and login or admin checks on each route. Also one user reading another user’s data, rate limits and spend caps, and dashboard settings. Our free guides cover these until the checks ship.
LimitNo findings here doesn’t mean these are handled.
HONEST LIMITS
An empty report means none of Aster’s checks matched. It isn’t a security clearance. If your app handles money or sensitive data, get a specialist review too.
ASTER IS
ASTER ISN’T
YOUR REPORTS
Your latest report stays in your account on every plan, and you can download it any time. Your profile and reports are encrypted at rest.
QUESTIONS
Here’s exactly what happens. Aster gets read-only access to the repos you pick. Files are read in memory; nothing is cloned, installed or run. No AI reads your code during an audit, and no copy of your repo is kept. You can revoke access in GitHub any time.
Not during an audit: the Aster Code Audit App can’t write. If you authorize Aster Fixes separately, it can open a draft pull request on a new branch after you confirm the change. Nothing is merged automatically.
Not for audits. For a fix, Aster first shows the model, the files and the most it can cost. After you confirm, those files and findings go through OpenRouter to the model you chose. The route has zero data retention: the provider keeps no copy. Known key patterns are masked, but check the preview.
No. Files are read into memory for the audit, and no source archive is saved. Your report is saved to your account, with file names, findings and scan limits.
Your browser opens the zip and sends only the files Aster checks: code, config, database rules and env files, compressed. Aster runs the same checks in memory during that request and saves only the report. The upload isn’t stored, and no AI reads it.
No. We make no SOC 2 claim, and a code report can’t establish SOC 2 or any other compliance. Audits don’t include load testing either.
Only marketing pages use analytics (Vercel Web Analytics and Speed Insights). Signup, recovery, audit and dashboard pages are excluded. Your source, findings and report downloads are never sent as analytics events.
Disconnect GitHub in the dashboard to cancel active work. Then revoke or uninstall the App in your GitHub settings. Deleting your account removes active account records and retained reports. Privacy Policy
Choose the repository. Read what comes back. 1 free audit every month, read-only from the first click.