VibeScale status
Answered our latest tool-list check 22 hours ago with 3 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 12:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 12:17 | Answered | 1.7 s | 3 |
Tools (3)
Read from the server on 16 Nov 2026.
- scan_app_launch_readiness
- Reads one public web app the way a browser does (its HTML, the same-site scripts it loads and any source maps they point to) and reports what any visitor can already see: server secret keys shipped to the browser (Supabase service_role, OpenAI, Anthropic, Stripe, AWS, GitHub, SendGrid, Resend; shown masked), a published source map, no HTTPS, and missing Content-Security-Policy, HSTS or frame prote
- lint_supabase_rls
- Reads Supabase SQL (migrations or a schema dump) as text and lists tables in exposed schemas without row level security, RLS with no policy, policies that allow everything or read user_metadata, policies without a role, write grants to anon, SECURITY DEFINER functions and views, new tables without a grant, and public storage buckets, each with SQL that fixes it. Use when someone asks whether their
- check_env_exposure
- Takes environment variable NAMES (never values) and says, for each one, whether the build tool ships it to every visitor (VITE_, NEXT_PUBLIC_, EXPO_PUBLIC_, REACT_APP_, PUBLIC_, GATSBY_, NUXT_PUBLIC_) and whether its name looks like a server secret that must not be there. Use when someone asks whether their .env or API keys are exposed in a Lovable, Bolt, Vite, Next.js or Expo app. Send names only