Vibe coding security scanner compare: repo, live URL, and ship-flow

Before you share the link, run a Ship Read on the repo, folder, or ZIP you are about to ship. If you only have a deployed URL, paste it at /app for the outside-view read, then clone the repo for the full read and push gate. Dedicated URL scanners add passive posture checks Seatbelt does not claim. If you handle payments or customer data, do not treat a clean URL scan as permission to skip the repo read.

No. CheckVibe and peers run passive or runtime URL probes. Seatbelt also grades live URLs via outside-view static read (observation framing, honest limits), but the wedge is six-surface plain English at repo handoff plus optional push gate. Use both if you want deep URL posture and ship-moment proof.

ShipSafe sells independent verification with MCP in-editor scans and paid GitHub URL reads. That is a strong outside-in lane after commit. Seatbelt reads the artifact before launch, returns a plain-English six-surface report, and can park flagged pushes. Many teams want both layers.

vibe-check-cli covers broad SAST and secret rules with a PR comment bot. Seatbelt prioritizes six ship-killers in founder English and produces a shareable report URL at handoff. Breadth and triage are different jobs; you can run both.

REA runs a probabilistic Codex review for fleet policy. Seatbelt is a deterministic static read of six surfaces with exit codes and a shareable report. Fleet stacks often use both: LLM review for governance, artifact read for launch-day ship-killers.

Respect it. npm audit catches dependency CVEs, not RLS-off migrations, client Stripe keys, or unsigned webhooks. CodeRabbit Pro runs real AI line-by-line PR review on GitHub and GitLab ($24/dev/mo annual; free tier is summarization and IDE/CLI only, Jul 2026). Under agent-heavy PR volume, fair-usage throttle at the 95th percentile degrades Pro from 5 to as low as 1 review/hour at 60+ reviews in seven days. When rate-limited, CodeRabbit posts a comment and a Review rate limited check that passes by design: it never blocks merge on protected branches (official Fair Usage Limits Policy). Probabilistic diff review on the PR is not a deterministic six-surface artifact read at ship moment. Seatbelt reads keys, database rules, auth, payments, customer data cues, and risky shortcuts in founder English, with optional push gate and shareable proof strangers verify at handoff. Many teams want both.

Platform checks are real but platform-scoped. Platforms differ, no one default covers every builder. v0 has the strongest default gate: Vercel blocks insecure v0 deploys automatically, no setting to turn on. Lovable and Replit share the opt-in critical block band: Lovable workspace admins can enable "Block publishing with critical findings" on all plans (off by default), and Enterprise workspaces can enable a second opt-in "Block publishing with PII" when Sensitive data scanning is on. Replit always runs a security scan before publishing and offers opt-in Block publishing of critical vulnerabilities under Deploy → Advanced (off by default; Replit Project Security Center, July 2026): when On, publish blocks on critical severity until you fix or dismiss; dismissed findings unblock. Both Lovable gates and Replit's toggle are in-platform only and off by default; the shareable proof there is an Aikido connector report shaped for SOC 2 questionnaires, not a plain-English ship read. In April 2026 a platform API regression let any authenticated Lovable user read chat history and source on legacy public projects (Feb 3 through Apr 20; fixed Apr 20, per Lovable's incident response). That post also documents that researchers filed valid HackerOne reports starting Feb 22 that were closed without escalation because stale triage documentation still described public chat visibility as intended until a public disclosure Apr 20. That episode was broken access control on shared infrastructure and a disclosure-process miss, not ship-moment gating and not something either opt-in publish block would catch on a cross-platform export. Bolt is the opposite false-green: when it finds nothing or you fixed issues, the Publish menu shows No security issues (Bolt support publish, July 2026). That green line is confidence copy, not v0's deploy block. If issues remain, Bolt alerts with Review security; the publish flow never stops. Base44 sits at the bottom: manual Run Security Scan (not on deploy), no publish block, and Ignore hides findings from the next scan so a green rescan can read false-clean. Base44's own application-security guide prescribes SafeVibes as step 1 of an external URL loop before the in-platform check. Wiz and Aikido deep scans in-platform still do not gate a git push from Cursor or any other host. Either way the gate lives inside one platform's deploy lane. Push from Cursor or any other host and nothing checks the artifact you hand off. Export the synced GitHub repo, rotate if exposure is plausible, and run a ship-moment read before you share. Seatbelt gates your push wherever you build and returns the shareable report at freelancer handoff.

v0's gate is real and on by default. Vercel reports over 100k insecure deployments blocked, including 17k in 30 days on exposed secrets alone, with NEXT_PUBLIC_ variable misuse the top blocked class (Vercel blog, August 2025). Respect it. It covers the v0 to Vercel deploy lane, focuses on secrets and config, and produces a block, not a shareable report or badge. Export the repo or build anywhere else and nothing gates the push. Seatbelt reads the artifact on any platform and returns proof you can hand off.

Bolt's Security Audit tab scans database rules and secrets inside Bolt, runs automatically on publish, and offers one-click fixes. When Bolt finds nothing or you fixed issues, the Publish menu shows No security issues (Bolt support publish, July 2026): a green confidence line, not a deploy block like v0's automatic Vercel stop. If issues remain, Bolt alerts with a Review security link to Settings; the publish steps never block. Export to GitHub or push from Cursor and nothing gates the artifact. You still need a ship-moment read with shareable proof at handoff.

Replit always runs a security scan before you publish. Respect it. Opt-in Block publishing of critical vulnerabilities (Deploy → Advanced, off by default) blocks on critical severity until you resolve or dismiss; dismissed findings unblock publish (Replit docs, July 2026). Security Agent grades in-platform only. No shareable plain-English cleared-report link at handoff. Sync to private GitHub, clone, and path-scan the checkout (never a Repl URL). That export path is still ungated. Seatbelt reads the artifact at the push boundary with proof you can forward.

Base44's Security tab runs on all plans, including free: data permission gaps, exposed credentials, login gaps, package vulns, and security headers, with one-click Fix. The scan is manual (Run Security Scan in Dashboard → Security), not automatic on deploy, and it does not block publish. Ignore moves an issue to Ignored and it will not reappear on the next scan, so a green rescan can read false-clean after you dismissed a real gap. Base44's own application-security guide prescribes SafeVibes as step 1 of an external URL loop before the in-platform check. SafeVibes is their endorsed outside view; Seatbelt is cross-platform ship read plus shareable proof link strangers verify when you export or clone and push from Cursor.

ScanMyVibe offers four free URL scans per month with no signup, passive/runtime URL probe. Seatbelt also accepts a live URL at /app (outside view). The full six-surface read, shareable proof, and optional push gate need the repo, folder, or ZIP export.

Scanbee unifies DAST, SAST, SCA, CSPM, and vuln assessment in one free dashboard, with Supabase JWT inject for auth routes. That is a strong post-connect probe. Seatbelt Ship Read covers repo, folder, ZIP, and outside-view URL, six-surface report and optional push gate on the repo export. Dashboard sprawl and ship-moment gate are different layers.

ScanVibe offers unlimited free URL scans with no signup, plus Pro at $9/mo for monitoring and badges, URL-first passive checks. Seatbelt also grades live URLs at /app. Repo export unlocks the full read and push gate; outside view alone uses observation framing.

Mosai Scanner runs 78 passive URL checks on a live site, with 15 free in about 60 seconds. Seatbelt also accepts a live URL at /app, outside-view static read, not Mosai-class passive breadth. Repo export: six ship-killers in plain English, shareable report, optional push gate.

vibecop runs 35 ast-grep detectors with a GitHub Action PR gate that can request changes, and one command sets up hooks for 7 coding agents. That is strong repo lint breadth for code quality. Seatbelt triages six ship-killers in founder English at handoff and can park flagged pushes before launch. Lint breadth and ship-killer triage are complementary; many teams run both.

Vibe Owl consolidates code, deps, env, and hook status into a PASS/FAIL inside VS Code or Cursor. That verdict stays in the editor. Seatbelt returns a shareable report URL at handoff and can park flagged pushes when you export to GitHub or ship from another tool.

ChakraView runs a thorough OWASP Top 10 pass in the terminal. That is great for power users who want breadth. Seatbelt is the six ship-killers in founder English at the handoff moment: keys, RLS, auth, payments, customer data cues, and risky shortcuts. Complementary layers.

Aikido MCP runs deterministic SAST and secret scans on snippets inside the IDE. That is a strong enterprise in-editor lane. It does not prioritize the six surfaces AI-built apps actually get hurt on: RLS-off migrations, unsigned webhooks, client Stripe keys, and leftover admin routes in plain English.

goodvibesonly runs a PreToolUse gate when Claude tries to commit. Terminal commits, other agents, and human pushes can bypass a session-only hook. Seatbelt reads the repo artifact and gates every push path, including --no-verify bypass classes when wired with deny hooks.

SecurityWall walks 44 manual checks in the browser with a score bar. Respect the thoroughness: that is an afternoon. Seatbelt is the 60-second automated six-surface read before you share the link. Triage front door, not a checklist replacement.

Most tools cover one or two layers. Seatbelt runs repo, folder, ZIP, and live URL outside-view Ship Reads, six surfaces in plain English, shareable proof, optional push gate. Dedicated URL scanners add passive posture depth and runtime crawl. DAST (Perfai) is a different job again. Match the tool to the moment; do not treat a URL-only read as permission to skip the repo export. See a repo sample report and an outside-view sample report. The full method is public: how Seatbelt scans.

Deterministic rule hits are real value. They are not the same as ship-killer prioritization in founder English. vibe-check-cli covers broad SAST breadth with a PR comment bot. Seatbelt triages six surfaces, parks flagged pushes, and returns a shareable report URL at handoff. You can run both.

Shiplight owns the parent "how to test a vibe-coded app before launch" query with a 10-step workflow where security is step 10. Seatbelt automates that security step: a plain-English six-surface read before you share the link. Adjacent, not competitive.

Respect it. Perfai's live-attack DAST lane finds real access-control breaks on a deployed URL. That is a different layer than a static read of the ship artifact before the link goes out. Perfai's own launch reviews concede the black-box motion's costs: browser automation loops bottleneck on rate-limiting firewalls and MFA gateways; the Fix Agent "addresses symptoms rather than underlying software designs," and merging auto-generated patches without senior structural oversight risks convoluted dependency layers (Product Hunt reviews, Daniyal Khamzin, Jul 2026). Seatbelt reads what you are about to ship, in git, before you share the link: no attack traffic, no auto-merged patches, human keeps structural judgment, shareable proof link.

The URL scanner cluster is crowded: per-scan pricing ($5-$19), subscriptions ($9-$99/mo), Mosai's pay-per-report unlock at R$47, free DB-exposure scans like SafeVibes ($0, maps exposed tables and write access from an anonymous outside view; Jul 2026), trust-score bundles like VibeProof (SEO + security + UX in one post-deploy grade; Solo Launch $4.99/mo with moltbot75 promo, Jul 2026), and headers-only free tiers like ShipSecure (1 of 6 checks on $0, 5 scans/mo, no shareable reports; Jul 2026). Full runtime now races down to $7.99/mo on ShipSecure Pro. Respect what they do: passive checks, TLS, sometimes runtime crawl. Mosai's own FAQ says they do not authenticate or test IDOR, tenant isolation, or internal access controls (scan.mosai.com.br). Seatbelt also accepts a live URL at /app (outside-view read, observation framing) but does not claim Mosai-class passive breadth. The wedge is six-surface plain English on the repo you export, shareable proof, optional push gate. Not a cheaper URL scanner.

Respect it. VibeProof and peers run a real outside view after deploy: exposed keys in client bundles, unprotected endpoints, TLS, and more. VibeProof bundles security with SEO, mobile UX, and performance into one Trust Score (50+ checks, AI fix prompts, Solo Launch $4.99/mo with moltbot75 promo, Jul 2026). That post-deploy grade is genuine value for live-site hygiene. Seatbelt is a different moment: a six-surface plain-English read of the artifact in git before you share the link, with optional push gate and a shareable proof report strangers verify at handoff. A runtime SEO+UX mixed into a security score after deploy is not the same layer as ship-moment read on what you export. Many builders want both. See repo and URL samples.

Respect it. SafeVibes is a real free URL scan focused on database exposure: exposed tables, record counts, and write access from an anonymous outside view (Jul 2026). Base44's own application-security guide prescribes SafeVibes as step 1 of a security hardening loop before the in-platform Security tab. That external validation lane is genuine. Seatbelt is a different moment: a cross-platform ship read on the artifact in git at the push boundary, with optional push gate and a shareable proof link strangers verify when you export or clone. External anonymous-access grade after deploy and artifact read before you share the link are different layers. Many Base44 builders want both.

Respect it. VibeDoctor runs 149+ checks on a GitHub repo and live site in ~30s, with a Launch Audit $9 one-time that ends in a plain-language is-this-safe-to-launch verdict and MCP in Cursor, Claude Code, Copilot, and Windsurf (Jul 2026). That launch-verdict lane is real. Seatbelt is a different moment: a static read of your local artifact at the push boundary with optional push gate and a shareable proof link strangers verify at handoff. Their Guard tier adds AI PR review on GitHub; that is not the same as six ship-killers in founder English on what you export. Many teams want the launch audit and the push-boundary read.

Respect it. ShipSecure Pro at $7.99/mo is the cheapest full runtime URL scan tier in this cluster: six checks in ~30s with shareable reports (Jul 2026). Their free tier is headers-only: one of six checks, five scans per month, no shareable reports. That is an honest freemium wedge, not unlimited free scanning. Seatbelt also accepts a live URL at /app (outside view) but the ship-moment wedge is six surfaces on the repo you export, shareable proof, optional push gate. Runtime crawl after deploy and artifact read before you share the link are different layers.

Respect it. VibeCheck on notelon.ai runs a real dual lane: Source Code Scanner via GitHub API and Live Site Scanner on headers, exposed files, CORS, cookies, and SSL. Free letter grade, no signup. Seatbelt also grades live URLs at /app and runs the full read on repo/folder/ZIP, shareable proof strangers verify, optional push gate, six surfaces in plain English. Grade in-browser vs proof at handoff. See repo and URL samples.

Respect it. Vibe Check on didyouvibecheck.com runs five review layers with 2-of-3 model agreement before a finding ships, OWASP Top 10 (2021) and CWE mapping, and badge-ready shareable reports at score 90+. Free tier for small public repos; paid job packs from $5 (Jul 2026). That agreement gate and badge artifact language is genuine value. Seatbelt is a different moment: a static read of your local artifact at the push boundary, not a score on a public clone. Six surfaces in plain English, optional push gate, shareable proof link strangers verify at handoff. Many teams want the badge and the push-boundary read. See a repo sample report for ship-moment proof.

Respect it. OX Security VibeSec embeds org security context into AI editors at generation time inside org-managed editors (September 2025). That is real prevent-at-source AppSec for teams on a fleet editor stack. Seatbelt is a different moment: a cross-platform ship read on the artifact in git at the push boundary, with optional push gate and a shareable proof link at freelancer handoff. OX does not gate git pushes from Cursor on exported repos, and does not produce plain-English proof strangers can verify. Many enterprise stacks use both: generation-time guardrails in the editor, ship-moment read on what leaves git.

Five different names collide on "VibeSec" as of July 2026. vibesec.app (Product Hunt "launching soon") is listed as coming soon; we could not verify a shipped product as of July 2026. PyPI vibesec CLI v0.7.0 by AyushkhatiDev is a real shipped OSS rules-and-hooks scanner (SARIF, enforcement hooks). OX Security VibeSec is enterprise prevent-at-generation inside org-managed AI editors. vibesec.sh sells a paid agent skill file; vibesecai.app is a separate landing. A dead Cursor forum guide still promotes "VibeSec-Skill": builders searching the word often land in the wrong lane. Seatbelt does not claim to be any of them. It is a six-surface ship read on your local artifact with shareable proof at handoff.

Respect it. PreToolUse hooks, Cursor beforeShellExecution denylists, and agent-control stacks like Aura (git-native IDE with proof-ledger commits via hooks, July 2026) are real for in-session catastrophic mistakes. Anthropic permissions docs say rules are enforced by the harness, not the model. Session hooks block commands at the harness layer. They do not read the six-surface build you export. A documented gap: PreToolUse hooks silently skip Bash from subagents spawned via the Agent tool (anthropics/claude-code#43612, closed not_planned May 2026). Terminal commits, other agents, and human pushes can bypass session-only hooks. Seatbelt is a different moment: a cross-platform Ship Read on the artifact in git at the push boundary, with optional push gate and shareable proof strangers verify at handoff. Many fleet stacks use both: session hooks for blast radius, artifact read for what leaves git. See a repo sample report for ship-moment proof.