---
title: "I Will run a pre-launch security check on your Lovable, Base44, Bolt or Supabase app, with a pass or fail report"
url: https://zinnhub.com/zinns/i-will-run-a-pre-launch-security-check-on-your-lovable-base44-bolt-or-supabase-app-with-a-pass-or-fail-report/
description: "In 1 to 3 days: a scripted pre-launch security check on your Lovable, Base44, Bolt or Supabase app, with a plain-language pass, warn and fail report. This is a scripted check, not an AI vouching for the app, and not a penetration test or a certification."
published: 2026-11-17T15:40:11+00:00
modified: 2026-11-17T15:40:11+00:00
language: en-GB
---

# I Will run a pre-launch security check on your Lovable, Base44, Bolt or Supabase app, with a pass or fail report

Ready in 1 to 3 days, depending on the package. A Lovable, Base44, Bolt or Supabase app can look finished and still ship with missing security headers, a public .env file, a secret key in the JavaScript, or a database table that anyone can read. Most owners never see this, because the app looks fine in the browser.

Crom Services runs a fixed script against your live or staging URL and gives you a clear pass, warn and fail report, with evidence and the fix in plain words. The proof is the script, not an AI writing an opinion.

What you get:

- A scripted check of security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) and the HTTP to HTTPS redirect
- A check for exposed files such as .env, .git and backup files, and for public JavaScript source maps
- A CORS check, and a scan of the public JavaScript for secret keys. The report shows the key type and the first 4 characters only, never the value
- If the app uses Supabase: a read-only list of tables visible to the public anon key, and a flag on any table that returns a row to an anonymous user (LIMIT 1, no writes)
- A gentle rate-limit check: at most 20 requests to one endpoint. Not a load test
- A Markdown and HTML report with pass, warn and fail, evidence, and the fix in plain words

What we need from you:

- The live or staging URL
- If the app uses Supabase and the public key is not already in the page, the project URL and the anon or publishable key only. Never the service\_role or secret key
- Which site is in scope, if you have more than one

How it runs: you order and send the URL, we run the script and review the report. On Scan + fix list you also get a plain list of what to change, in order. On Scan + fixes we apply the safe fixes we can, run the script again and send both reports.

Fully remote. No calls needed; questions and handover happen in the order messages.

Fixed price. If it doesn’t work as agreed, we fix it free within 7 days of handover. We won’t leave you with something broken that we built. The clock starts once we have the URL and any key we need.

Not included, and said plainly: this is a scripted pre-launch check. It is not a penetration test, not a certification, and not a guarantee the app is secure. It does not cover social engineering, paid third-party scanners, or a full source-code review. We quote that work separately so you know the price first.
