Build with your agent. Check what is live.
Start with a free passive scan. Find exposed credentials and risky web configuration. Give your coding agent the evidence, deploy your repair, and use a scoped recheck for supported header findings.
- Tanpa daftar
- 230+ passive checks per scan
- Paham BaaS
- Aman untuk auth (pasif)
FixVibe is a security scanner for indie developers and small teams shipping web apps built with AI coding tools such as Lovable, Bolt, v0, Cursor and Claude Code. Paste a deployed URL to find exposed Supabase service-role keys, missing Row-Level Security, open Firebase rules, secrets in JavaScript bundles and weak headers. The passive scan is free.
How it fits your workflow
Your agent repairs it. Recheck the deployed header.
Start with a precise result you can inspect. The first verification pilot checks whether a supported x-content-type-options finding has been repaired on the same deployed page. Your agent makes the change; FixVibe measures the follow-up response.
This workflow example is currently available in English.
- 01
Inspect the deployed app
Run an authorized passive URL scan. A new supported header finding can provide the baseline for a scoped recheck. Review the report's evidence and any checks that could not run.
- 02
Repair in your existing workflow
Open the finding's fix-and-recheck options. Give the repair guidance to Claude, Codex, or your preferred agent, review its change, and deploy through your normal workflow.
- 03
Deploy, then request verification
See whether the expected header is present on a comparable response. The result can confirm this scope, report the issue still present, or stay inconclusive when a reliable comparison is not possible.
Synthetic example · not a customer report
Before: x-content-type-options is missing. After a comparable recheck: x-content-type-options: nosniff.
Illustrative result: “Verified for this page and header.” The report keeps the baseline, the later measurement, and any remaining responsibilities visible.
This pilot verifies one header on the same page's anonymous response. Other pages, signed-in roles, credential revocation, and unrelated vulnerabilities remain outside that result. It is not an app-wide security certificate.
Free reports show a top-two preview. For one eligible finding, the browser introduction includes repair guidance and one verification within seven days, plus one additional attempt after an inconclusive result. Full reports and API/MCP require a paid plan; scheduled scans require Pro or Unlimited.
Cakupan scanner
- 240+
- kelas kerentanan tercakup
- 230+
- check pasif / scan
- 130+
- check aktif / scan
- 190+
- check GitHub / scan
Kompatibel dengan
A security check alongside your coding agent.
Coding agents can review and test security. FixVibe adds maintained checks, deployed-app evidence, and repeatable reports to your workflow. URL scans, eligible GitHub scans, and paid MCP access each have their own scope.
- Cursor
- Claude Code
- OpenAI Codex
- GitHub Copilot
- Lovable
- Bolt.new
- v0
- Replit Agent
- Windsurf
- Devin
- Google Jules
- Gemini CLI
- Firebase Studio
- Amazon Q Developer
- JetBrains Junie
- Kiro
- Tabnine
- Qodo
- Sourcegraph Amp
- Continue
- Cline
- Roo Code
- Aider
- OpenCode
- Base44
- Anything
- Builder.io Fusion
- Tempo
- Softgen
- Trae
Guides
Secure your AI-built app.
- Keamanan BaaS
Scanner RLS Supabase: temukan tabel dengan row-level security yang hilang atau rusak
Row-level security (RLS) adalah satu-satunya hal yang berdiri antara data pelanggan Anda dan internet ketika Anda merilis aplikasi berbasis Supabase. AI coding tools menghasilkan kode berbentuk RLS yang ter-compile, terkirim, dan diam-diam membocorkan data — tabel dibuat tanpa RLS diaktifkan, policy yang membaca tetapi tidak pernah membatasi, predikat yang membandingkan kolom dengan dirinya sendiri. Artikel ini menunjukkan apa yang dapat dibuktikan scanner RLS Supabase dari luar, empat bentuk RLS rusak yang muncul di aplikasi vibe-coded, dan cara men-scan deployment Anda sendiri dalam kurang dari semenit.
- Keamanan BaaS
Supabase service role key terekspos di JavaScript: apa artinya dan cara menemukannya
Service role key Supabase adalah kunci master ke database Anda. Siapa saja yang memegangnya mem-bypass Row-Level Security, dapat membaca setiap kolom dari setiap tabel, dan dapat menulis atau menghapus apa pun yang mereka pilih. Ia dirancang untuk hidup secara eksklusif di kode sisi server — tidak pernah di browser. Ketika AI coding tool mengirimkannya ke bundle JavaScript, database Anda, secara efektif, bersifat publik. Artikel ini menjelaskan bentuk JWT yang mengidentifikasi key yang bocor, tiga pola AI tool yang menghasilkan kebocoran, apa yang harus dilakukan pada jam pertama setelah deteksi, dan cara men-scan secara otomatis sebelum pengguna melakukannya.
- Keamanan BaaS
Scanner aturan Firebase: temukan aturan Firestore, Realtime Database, dan Storage yang terbuka
Aplikasi Firebase gagal dalam keamanan dengan satu cara yang konsisten: aturan allow read, write: if true; yang tersisa dari quickstart mode test, tidak pernah diganti sebelum produksi. AI coding tools menghasilkan aturan-aturan ini verbatim dari contoh dokumentasi dan jarang meminta pengembang untuk mengeraskannya. Artikel ini menunjukkan bagaimana scanner aturan Firebase mendeteksi aturan terbuka di Firestore, Realtime Database, dan Cloud Storage dari luar proyek — dan cara memperbaiki apa yang ditemukannya.
- Panduan keamanan
Checklist keamanan vibe coding: 51 item sebelum rilis
Daftar periksa praktis dan bertahap untuk aplikasi yang dibuat dengan Cursor, Claude Code, Lovable, Bolt, v0, Replit, dan Windsurf. Setiap item dapat ditindaklanjuti dalam waktu kurang dari lima menit. Jalankan sebelum Anda mendorong ke produksi, lalu jalankan lagi sebelum setiap rilis besar. Item dikelompokkan ke dalam tujuh kategori — rahasia, database, autentikasi, header, pihak ketiga, penerapan, pemantauan — dan ditandai dengan fase penerapan item tersebut.
- Panduan keamanan
Lovable security checklist: 25 items before launch
Lovable is a fast path from idea to a published full-stack app on Supabase and Vite. This checklist targets the risks that come with that stack: RLS that must be enabled and tightened on every table Lovable creates, test keys from integrations, import.meta.env leaking env vars into the Vite bundle, GitHub sync exposing secrets, and missing security headers. 25 items across secrets, database, auth, headers, deployment, and Lovable-specific gotchas.
- Panduan keamanan
Bolt.new security checklist: 23 items before ship
Bolt.new (StackBlitz WebContainer) runs your dev environment in the browser, generates full-stack JS in minutes, and publishes to Bolt hosting by default or to Netlify (Bolt docs). This checklist targets Bolt-specific risks: secrets that were safe in the dev container leak once the project is exported, Express CORS defaults are permissive, session cookies need explicit HttpOnly flags, and credentials pasted into the terminal or chat are hard to take back. 23 items across secrets, database, auth, headers, deployment, and Bolt-specific gotchas.