INTEGRATIONS
Built with Lovable or Cursor?
On GitHub or in a zip, Aster checks it.
Connect GitHub read-only, or upload your project as a zip if it isn’t on GitHub. Aster checks it today, whatever AI tool built it. Editors, trackers, chat and CI are planned and labelled that way.
GitHub is connected to Aster today. GitLab, Bitbucket, VS Code, Cursor, Slack, Linear, Jira and GitHub Actions are planned and not yet available.
THE DIRECTORY
Every integration.
Honestly labelled.
GitHub works today. The rest are planned, and your requests decide what comes first. Each one will ask for its own access when it becomes available.
16 integrations · 1 available · 15 planned
-
AVAILABLE
GitHub
Read-only access to the repos you pick. Findings with file and line, and fixes as draft pull requests you approve.
Git platformsConnect GitHub -
PLANNED
GitLab
Would let you audit a GitLab project, read-only, the same way as a GitHub repo today.
Git platformsRequest -
PLANNED
Bitbucket
Would let you audit a Bitbucket repo, read-only, the same way as GitHub.
Git platformsRequest -
PLANNED
Azure DevOps
Would let you audit code in Azure Repos, read-only, the same way as GitHub.
Git platformsRequest -
PLANNED
VS Code
Would show each finding on its exact line in your editor, so you fix it where you code.
Code editorsRequest -
PLANNED
Cursor
Would hand a finding to Cursor’s agent with the file, line and fix steps. No copy-paste.
Code editorsRequest -
PLANNED
Windsurf
Would bring findings into Windsurf, so Cascade can fix them with the file and line in view.
Code editorsRequest -
PLANNED
IntelliJ IDEA
Would show each finding next to the line it’s about, inside IntelliJ IDEA.
Code editorsRequest -
PLANNED
Linear
Would turn a finding into a Linear issue with the file, line and fix steps filled in.
Issue trackingRequest -
PLANNED
Jira
Would turn a finding into a Jira ticket your team can plan, with the file and fix steps.
Issue trackingRequest -
PLANNED
Azure Boards
Would turn findings into work items, so fixes get tracked like the rest of your work.
Issue trackingRequest -
PLANNED
Slack
Would post a short summary to the channel you pick when an audit ends: what to fix first.
Team notificationsRequest -
PLANNED
Microsoft Teams
Would post a short audit summary to a Teams channel, critical findings first.
Team notificationsRequest -
PLANNED
Email
Would email you a short summary after each audit, critical first, with a link to the findings.
Team notificationsRequest -
PLANNED
GitHub Actions
Would run an audit on each push or pull request, so a new leaked key shows up before you merge.
CI / CDRequest -
PLANNED
Jenkins
Would run an audit as a step in your Jenkins build and show what it found.
CI / CDRequest
Nothing available here yet.
Every integration in this category is planned. Tell us which one you need first.
Planned integrations are not yet available to connect, and we don’t promise dates. Logos identify the named tools; they don’t imply partnerships.
GITHUB · AVAILABLE TODAY
Read-only to look.
Opt in to fix.
Audits use the Aster Code Audit App. It can only read the repos you share with it. Fixes use a second, optional app, Aster Fixes. You add it only when you want a draft pull request.
- You choose the repositories in GitHub
- Nothing is merged automatically
- Revoke or uninstall either app in GitHub settings
- ContentsRead
- MetadataRead
- Pull requestsNo access
- WorkflowsNo access
Aster reads your files in memory and checks them. Nothing is cloned, installed or run. No AI reads your code during the audit.
- ContentsRead & write
- Pull requestsRead & write
- WorkflowsNot requested
- MergeNever automatic
You review the patch and confirm before Aster opens a draft pull request on a new branch. If the branch changed since the audit, Aster asks for a fresh audit first.
SOURCE COVERAGE
What the checks read today.
And what they don’t yet.
Pick your stack to see what Aster checks today, and what it doesn’t. Aster reads your files; it never runs them.
.js · .mjs · .cjsA closer look at your JavaScript.
Leaked keys and selected risky patterns, file by file.
- Code that won’t parse (syntax)
- Text run as code (eval)
- Skipped connection checks (TLS)
- Queries built from user input (SQL)
- Leaked keys and secrets
- Keys in every browser (public env)
Outside this checkRunning your code, or a full lint.
.ts · .mts · .ctsRead the code behind the types.
Aster reads your TypeScript without building your app.
- Code that won’t parse (syntax)
- Leaked keys and secrets
- Risky calls like eval or raw SQL
Outside this checkA full type check. It doesn’t replace your compiler.
.jsx · .tsxGive your components a second look.
Aster reads your JSX and TSX files for patterns worth a second look.
- Code that won’t parse (syntax)
- Leaked keys and secrets
- User text run as code (unsafe HTML)
Outside this checkComponent rendering, browser testing and a complete React ruleset.
Client / serverKeep server secrets on the server.
Aster follows relative imports from each “use client” file and flags server-only code. It also checks NEXT_PUBLIC_ variables for secrets.
- Server code pulled into the browser
- Keys in the browser (NEXT_PUBLIC_)
- Risky build settings
- Known holes (React2Shell, middleware bypass)
Outside this checkPath aliases, dynamic imports and framework build transformations.
Server sourceCheck the source behind your server.
Aster reads your API and server files for these risky patterns.
- Skipped connection checks (TLS)
- Forgeable login tokens (JWT)
- Other sites acting as users (CORS)
- Queries built from user input (SQL)
- Leaked keys and secrets
- Packages with known holes
Outside this checkLogin and admin checks on each route, webhook signatures, rate limits, and load tests.
Python · JSON · YAML · .envYour database rules, too.
Supabase migrations, Firebase rules, .env files and lockfiles. Any other text file is checked for leaked keys.
- Leaked keys and secrets
- Your passwords file in git (.env)
- Tables anyone can read (RLS off)
- Policies that let everyone in
- Public storage buckets
- Open Firebase rules or test mode
- Packages with known holes
- Python & Ruby queries and TLS
Outside this checkFull parsing of Python, Ruby and PHP, and settings made in the Supabase, Firebase or Vercel dashboards. Oversized and unsupported files are skipped.
Python
Java
Go
Ruby
PHP
Rust
C++
C#
Swift
Kotlin
Docker
Kubernetes
Terraform
Technology logos show source coverage, not account connections or partnerships.
HELP SHAPE WHAT’S NEXT
Missing your tool?
Tell us what to build next.
Tell us what you use and where Aster would help. Requests shape what we build next.
Opens your email app with a draft. Nothing is sent automatically.
Start with GitHub.
Start free.
Pick one repo. Aster reads it, read-only, and shows what’s exposed, critical first. 1 free audit every month, no card needed.
QUESTIONS
Connections,
clearly explained.
Which integrations can I use today?
GitHub. Connect it, pick the repos to share with the Aster Code Audit App, and run a read-only audit. Everything else here is planned.
What does “Planned” mean?
The integration is on our roadmap and not yet available to connect. We don’t publish dates. Each one will ask for its own access when it becomes available. Email us to tell us which one matters most to you.
What can Aster access in GitHub?
The audit app requests Contents: read and Metadata: read. It has no write permissions and cannot merge changes. Only repositories shared with the app and accessible to your account appear.
Can Aster push code to my repository?
Only if you install the separate, optional Aster Fixes app and confirm the change. It opens a draft pull request on a new branch for your review. Nothing is merged automatically, and workflow files are left for you to change by hand.
Does it work with Lovable, Bolt or Cursor?
Yes. Connect the GitHub repo, or download your project as a zip and upload it in your dashboard. Aster checks the code, whatever tool built it. Aster-drafted fixes and pull requests need GitHub for now.
Can I use Aster from Cursor or Claude Code?
Not yet. A Cursor integration and an MCP server are planned. Today you run audits in the dashboard and can paste any finding into your AI tool.
How do I remove access?
Use Disconnect GitHub in the dashboard to cancel active work, and revoke or uninstall the app in your GitHub settings to remove its authorization.
Which languages do the checks support?
Aster works best on JavaScript and TypeScript apps: React, Next.js, Node, Vite and Expo. It also reads Supabase SQL migrations, Firebase rules, .env files and lockfiles. Other text files, like Python, JSON and YAML, are checked for leaked keys.
Do you offer self-hosted or managed deployments?
Not yet. Other ways to run Aster are planned. If your team has specific hosting needs, tell us about them.