Environment values exposed in frontend output
A credential can move from a private workspace secret into a client-side bundle through an incorrect build-time prefix or import.
Security for Bolt apps
Check the security of your Bolt-built app
BoringSec evaluates the deployed application first and shows early evidence while deeper authorized engines continue. Source-only questions remain clearly separated from what a public URL can prove.
Run it before sharing a prototype publicly and after changes to auth, database rules, integrations or deployment configuration.
Run scans only on systems you own or are authorized to assess. Deep engines require verified authorization and may remain unavailable for a target.
report / sample findingIllustrative
High
Example report structure
Credentialed CORS response reflects an untrusted origin
- Evidence
- A bounded request using a scanner-controlled Origin receives that same origin in Access-Control-Allow-Origin together with credential support.
- What it means
- If sensitive endpoints share this policy, a malicious site may be able to read authenticated responses from a victim’s browser.
- Fix and verify
- Replace reflection with an explicit origin allowlist, reject unknown origins, remove credential support where unnecessary and retest.
This is an illustrative finding, not a result for your application. Live reports show the scanner, evidence state and coverage limits for the actual target.
Common risk paths
What deserves a closer look
These are risk patterns relevant to Bolt.new projects—not claims that every project has them. A finding appears only when a scanner returns supporting evidence.
Open backend rules
Supabase tables, storage buckets or Firebase databases can remain reachable even when the interface looks locked down.
Permissive cross-origin access
Broad or reflected CORS behavior can let an untrusted origin read API responses in a user’s browser.
Honest coverage
What each scan surface can prove
URL evidence, connected source and authorized deep engines answer different questions. BoringSec keeps those sources separate and shows partial, blocked and unavailable states instead of turning an untested surface into a pass.
Read the public methodologyDeployed web surface
Checks the public response path for TLS, security headers, DNS and email authentication, cookies, CORS, exposed files, technology signals and other externally observable controls.
Shipped JavaScript
Inspects bounded, same-origin frontend bundles for secret-shaped values and records partial coverage when an asset cannot be fetched or exceeds a safety limit.
Independent deep engines
Nuclei, OWASP ZAP and Medusa continue asynchronously only when the requested scan is authorized and the engine is available. Their running, blocked or unavailable state stays visible.
Repository context
A separately connected repository can add source-level evidence for committed secrets, auth and database risk patterns, dependency advisories and server/client boundary mistakes.
From observation to verification
A report built for the next action
- 01
Observe
Inspect the public response path and start eligible background engines.
- 02
Verify evidence
See what was observed, by which scanner and with what confidence.
- 03
Fix in context
Use a concrete remediation path and the Bolt-relevant context.
- 04
Retest
Run a fresh assessment; monitoring can detect later regressions separately.
Questions before you scan
Does BoringSec need access to my Bolt.new account?
No. A live scan starts from the deployed URL and observes only the public surface. Repository access is a separate, explicit connection and is not required for the URL scan.
What can a URL-only scan prove?
It can support findings with externally observable evidence such as response headers, TLS behavior, public files, shipped bundles and bounded backend probes. It cannot prove that private source code or authenticated workflows are safe.
Does a good score mean the application is completely secure?
No automated scan can prove complete security. BoringSec reports assessed, partial, unavailable and authorization-required coverage explicitly so a clean result is not presented as evidence for surfaces that were never tested.
Is BoringSec affiliated with Bolt.new?
No. BoringSec is an independent security service and is not sponsored by, endorsed by or affiliated with Bolt.new.
Check the deployed application, then verify every fix
Start with the public URL. Add source or authenticated context only when you choose to expand coverage.
Start a security scan