Built it with Cursor? Let's make sure it's safe to ship.

Cursor is great at making things move. It's less great at remembering you have a credit card on file. Here's what we look for in Cursor-built apps, and how we help you fix it before you launch.

What we look for first

  • API keys hardcoded into the repo
  • Admin pages with zero auth checks
  • /api routes one curl loop away from a surprise bill
  • SQL queries built by string concatenation

Illustrative examples. Yours might be cleaner. Or worse.

The Cursor mistakes we look for.

Four issues we check in every Cursor-built app, each with the change to make. If any of these sound familiar, you already know why this exists.

  • Keys Cursor pasted into your code

    Cursor can inline an API key straight from a tutorial snippet, and it ships with your code.

    Suggested change: Move each key to a server-only variable, then rotate it.

  • Server actions exposing your DB

    App Router server actions are easy to wire up wrong. Cursor sometimes skips input validation and the auth check.

    Suggested change: Validate the input and check the session in every action.

  • Routes with no rate limit

    Cursor-generated /api/chat endpoints are catnip for billing attacks.

    Suggested change: Require sign-in and cap requests per user.

  • NEXT_PUBLIC_ accidents

    Variables prefixed with NEXT_PUBLIC_ are visible to every visitor. Cursor doesn't always know which ones should stay private.

    Suggested change: Drop the prefix from anything secret and read it on the server.

How a review works.

Try the free key-leak scan first if you like. When you’re ready for the full review, it goes like this.

  • You share your code.

    Pay once, then send a GitHub link, a public repository URL, or a ZIP of your project.

    Day 0

  • We review it.

    We run AI-assisted security checks on your source, review the results by hand, and record what was and was not covered.

    Within 5 working days

  • You fix what matters.

    You get a prioritised report in plain English. On request, we send the fixes as a draft pull request or patch. You review, test and merge.

    When you’re ready

One price for one project.

Pay once for a review of a single repository. If your stack is bigger than that, we scope it with you first.

Launch scan

Pilot

One app, one repo, reviewed by a person.

  • High-risk issues that get apps exploited at launch
  • API keys, dependencies, config and AI-prompt checks
  • Fixes as a draft pull request or patch, on request
  • Reviewed by a person, delivered within 5 working days
  • Full refund if we cannot deliver a usable report
  • A shareable report for investors, teammates or yourself

Scope: one web app or API in a single repository (typical MVP size). Stacks: Node, TypeScript, React, Next.js, Python and most modern frameworks.

$299

One-off, per project. No subscription.

Start with a free lightweight preview, then buy a one-off review of one project. AI-assisted checks are reviewed by a person, and you get a prioritised report in plain English within 5 working days. Fixes can be sent as a draft pull request or patch on request. Review and test any change before you use it.

Payment is handled by Polar.

Deep dive

Custom, scoped together

For several codebases, real infrastructure or a growing team. We review services, environments, cloud, networking and CI/CD, and send a fixed proposal before any work starts.

Talk to us

Side by side

FeatureLaunch scanDeep dive
RepositoriesOneSeveral
TurnaroundWithin 5 working days1 to 2 weeks
Plain-English reportIncludedIncluded
Corrected ZIP or draft pull requestIncludedIncluded
Cloud and CI/CD reviewNot includedIncluded
Optional follow-up reviewsNot includedIncluded
Founder Q&A callNot includedIncluded

Ship it reviewed.

Book the review now, or leave your email and a person will reply within one working day. No commitment and no jargon.