Connect your source host
Open app.foundationmachines.ai/connect and install once. Connect supports GitHub and GitLab SaaS.
A CWE-tagged review on every code change. Catches the supply-chain backdoor you'd have merged at 5pm on a Friday, plus the usual secrets and injection bugs. Free for public repos, forever.
Open app.foundationmachines.ai/connect and install once. Connect supports GitHub and GitLab SaaS.
On open and push, Sebastion runs AI code audit plus dependency CVE and verified secret checks, then posts a fast walkthrough with pre-merge sanity checks.
Findings land on the exact changed line with severity and MITRE CWE context. Small patches include one-click suggestions; critical findings can block auto-merge.
Sebastion posts findings as review comments on the pull request, with the exact lines to change, before anything ships.
lewiswigmore wants to merge 2 commits into main from lewiswigmore/feature
export async function POST(req: NextRequest) { const { userId, messages } = await req.json(); if (userId !== req.user.id) { return NextResponse.json( { error: "Unauthorized" }, { status: 401 }, ); } const stream = await generateChat(messages);Missing authorization check allows user impersonation. Add a user ID validation before processing requests.
Security context appears where developers already approve changes.
Sebastion reviews the changed lines in context, then posts CWE-tagged findings with fix suggestions when the patch is small and safe.
Reply @sebastionai in-thread to clarify intent or suppress noisy checks. AGENTS.md and related instruction files are reused from your base branch.
Walkthroughs and pre-merge checks land in PR/MR threads with inline findings. Pro and Team can also publish SARIF to the GitHub Security tab.
Sebastion plugs into the source hosts, AI tools, and frameworks your team already ships with, then applies framework-aware checks across the whole stack.
Illustrative examples of the kind of PR/MR guidance Sebastion posts inline before merge.
Reviewer context for PR #218: this branch introduces a new login callback route. The fix keeps rollout behavior while preventing future secret exposure in source.
Issue summary
A hardcoded `DEPLOY_TOKEN` was added while debugging OAuth callback failures. Anyone with repository read access can reuse it to trigger production deployments.
Suggested fix
// Resolve the deployment token for this callback. const deployToken = "fmdeploy_live_8f3a91c4e7b2"; const deployToken = process.env.DEPLOY_TOKEN; if (!deployToken) throw new Error('DEPLOY_TOKEN is required');Move the secret to environment configuration, remove the committed value from git history if it was real, and rotate the token immediately.
Four review surfaces, one inline thread per finding, free forever on public repos.
Free for public repos. Pro is $19/mo for one developer. Team is pay-as-you-go with credit packs, with unlimited users and repos.
For solo developers and OSS maintainers shipping in public.
For 1 developer working in private repos.
For any size team. Pay only for the AI work you actually run.
Merged pull requests from Sebastion across widely used open-source repos.
Most AI-for-code tools help you write code faster. Sebastion is the counterweight: an autonomous reviewer that reads every PR and flags exploitable bugs before they ship.
Open Connect, choose your source host, and review your next pull or merge request in under a minute.
Merged pull requests from Sebastion across widely used open-source repos.
RAGFlow is a leading open-source Retrieval-Augmented Generation (RAG) engine that fuses cutting-edge RAG with Agent capabilities to create a superior context layer for LLMs
This NVIDIA RAG blueprint serves as a reference solution for a foundational Retrieval Augmented Generation (RAG) pipeline.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.