Sample report
Example scan report: plantpal-demo.example
This is a made-up example for a fictional demo app. It is not a real app, company or person, and no real site was scanned. It shows the format of a Warditor report and the kinds of issues the free scan checks for.
What the free scan found
OpenAI API key exposed in your JavaScript
A secret OpenAI key (sk-...abcd, masked) ships in the site's public JavaScript. Anyone can copy it and send requests on your account, so someone could run up your AI bill tonight.
Where: /assets/index-3f9c.js (the key is masked; we never store or show it in full)
Fix Pack fix: We move the key server-side (the OpenAI call goes into a server function so the key never reaches the browser), put the endpoint behind login, and add per-user caps, sent as a pull request. You rotate the key in your OpenAI dashboard (we walk you through it). Then we re-scan to confirm no key appears in your public JavaScript.
Anyone can read your Supabase database (Row Level Security is off)
Using only the public anon key from the site's own JavaScript, the table profiles could be read without logging in. Anyone can download those rows.
Where: Supabase table profiles (row contents are never stored or shown)
Fix Pack fix: We turn on row-level security for the exposed tables and add policies so users can read only their own rows, sent as ready-to-run SQL for you to review. Then we re-scan to confirm anonymous reads are blocked.
Your original source code is published via source maps
Source maps let anyone read your un-minified source code, comments and internal API routes.
Where: /assets/index-3f9c.js.map
Fix Pack fix: We turn off production source maps in your build config (Vite: build.sourcemap = false), sent as a pull request.
No Content-Security-Policy header
Without a CSP, a single injected script can run with full access to your page and your users' sessions.
Where: Response headers of https://plantpal-demo.example/
Fix Pack fix: We add a Content-Security-Policy that fits the scripts your app really loads, in your hosting config, as a pull request.
No Permissions-Policy header
Browser features such as camera and microphone are not explicitly turned off for your site.
Where: Response headers of https://plantpal-demo.example/
Fix Pack fix: We add a Permissions-Policy header alongside the CSP.
What passed
- No other API keys or secrets found in the JavaScript files checked
- No exposed
.env,.git, backup or config files - HTTP redirects to HTTPS; no mixed content
- HSTS, X-Frame-Options, X-Content-Type-Options and Referrer-Policy present
- No risky CORS settings
What a Fix Pack would do here
The Fix Pack fixes the issues from your scan (in this example, all five findings) within 48 hours of receiving access, or you get a full refund. You add the GitHub account warditor as a collaborator; for Supabase or Firebase we send the SQL or rules for you to run yourself, so we never need your database login, keys or user data. Each fix arrives as a pull request or SQL you review and merge, with a plain-English explanation of what changed, and we re-scan to confirm.
Every check shown is one the real scanner runs: exposed files, security headers, CORS, HTTPS and mixed content, source maps, secrets and AI keys in JavaScript, and read-only Supabase and Firebase probes. A clean result doesn't mean an app is secure; see the scanner terms.
Questions? [email protected].