GitHub Copilot started as autocomplete and now writes whole pull requests as a cloud agent. Either way, it is very good at continuing whatever pattern it sees, including the ones that were wrong to begin with.
I review the result as a system: what Copilot wrote, what it copied, and what nobody asked it to write. You get a ranked list of what to fix, each with a fix prompt you can hand to Copilot chat or the cloud agent.
1Line 1: If the variable is missing in production, every session token is signed with the word secret and anyone can mint one for any user.
Common problems in GitHub Copilot apps
Not every app has all of these. The report tells you which ones yours has, where, and what to do about each.
Critical
Fallback secrets that never got replaced
process.env.JWT_SECRET || 'secret' is a common completion. In production, one missing variable turns it into a password everyone knows. I check every secret, session key and signing key for a default value.
High
SQL assembled from strings
Completions for database code often land on template strings in $queryRawUnsafe or pool.query, because that is the shortest path to something that runs. I find each query that puts user input into the string itself and give you the parameterized version.
High
Middleware on most of the routes
An Express router where requireAuth sits on most endpoints and is missing from the two that were added last. I walk the full route table and say who can call what.
Medium
APIs from the version it saw most
Copilot often completes against the version of a library it has seen most, not the one in your package.json. Pages-style code inside the App Router, callback APIs next to promise ones, options that no longer exist. I check what you use against what you installed.
Medium
The pattern was copied, bug included
The fourth handler in a file is a near-copy of the third, down to the wrong field name or the off-by-one the third one had. I read the copies, not just the originals.
Low
Promises nobody waited for
A missing await in a completion compiles fine and works most of the time. The email sends after the response, the transaction commits before the check. I list every floating promise with the consequence of each.
Treatment plan
How it works
1
Book a check-up
Choose a tier and tell me where to send the report. Add your app's address if it is live. Two minutes, no sales call.
2
Show me your code
Pay by card, then give me read-only access to your code on GitHub (you paste in a key I send you) and let me into your app with test accounts. Never done that? I send you step-by-step instructions for your tool. I measure your app and confirm it fits before I start.
3
Get your diagnosis
Ready to launch, or not yet. Problems ranked, critical ones proven on your live app, each with a prescription for your AI tool. A PDF by email, then 7 to 30 days of questions by email.
4
Fix it, then a free follow-up
Fix the problems yourself, with your AI, or let me do it with the Fix Pack. Tell me within 30 days and I check once more that they are really gone.
No idea how big your app is? That’s normal, and you never have to count anything. Book the review you want; I measure your app before I start and tell you. If it doesn’t fit, you choose: upgrade, narrow it down, or a full refund. “Lines of your code” means the code you and your AI wrote, not the packages and UI kit your tool installed; many apps built with Lovable, Bolt or v0 fit the Safety Scan.
Start small, upgrade later. The Safety Scan’s price counts in full toward a Launch Review or Fix Pack for the same app within 30 days of your report.
Why this price? Software does the first pass, so you pay for the part only a person can do: checking every finding in your code, proving the critical ones and deciding what matters for your app. I take at most 3 Safety Scans and 2 Launch Reviews (or one Fix Pack) a week; if this week is full, yours starts the next.
Prices in US dollars, paid once, no sales call and no surprise invoice: anything extra is your choice, told to you before I start. The clock starts when I can see your code. Reports arrive as a PDF by email, in English, or German if you prefer.
Need a few things fixed after a scan? I fix by the hour at $199, three hours minimum, with the list agreed before I start.
Bigger than 50k lines, or a real mess? Rescue jobs are quoted, from $3,000, no obligation. Email me.
Not for you if
you have a team of engineers who already review each other’s code,
your app’s backend isn’t JavaScript or TypeScript (Python Replit apps, for example), or it is over 100k lines,
you handle regulated data (health records, banking, children), or need a pentest, certificate or compliance sign-off. Taking card payments through Stripe is fine.
A review lowers your risk a lot. It can’t guarantee that your app is secure, and nobody honest will say otherwise.
GitHub Copilot questions
My code is already on GitHub. What do you need?
Read-only access to the repository, and a note about which parts were written with Copilot if you know. I review the whole codebase either way, because the problems are rarely contained to one file.
Copilot already reviews my pull requests. Why a human?
An automated review is built around the diff in front of it. It will rarely tell you that the route added today has no auth because auth was never set up for that part of the app, or that three endpoints bypass the thing the fourth protects. I read the system, then the diff.
Can I apply the fixes with Copilot?
Yes. Each finding has a fix prompt with the files and the change spelled out. Paste it into Copilot chat, or hand it to the Copilot cloud agent as an issue and review the pull request it opens.
Why not just ask my AI to review it?
Do, and I will even give you the prompt. You will get a long list. What your AI cannot do is tell you which items are real, prove them against your live app, see your database and hosting settings, or check that its own fixes worked. If you cannot read code, that is the part you cannot do yourself either. It is what you pay me for.
I'm not a developer. Is this for me?
Yes, that is exactly who it is for. If you built an app with AI and cannot tell whether the code is any good, I check it and explain what matters in plain English. You never need to understand the code to act on the report: every problem comes with a prompt you paste into your AI tool. And you do not need to know what to ask. The report answers the questions you would have asked if you knew how.
How do I show you my code?
Most AI builders can push your app to GitHub, a free site that stores code. You give me read-only access by pasting a key I send you into your repository settings, which means I can look but not change anything. Never done it? After you book, I send you step-by-step instructions for your tool. A zip file works too. When the report is delivered, remove my access again; I remind you.
Is my code safe with you?
Every booking comes with an NDA, automatically. I never sell, publish or pass on your code. The only other party that sees it is the AI provider that helps with the first pass, under terms that do not allow it to train on your code. I never need your passwords or your live database, and I delete my copy within 7 days of delivering the final report.
From $149 for the first 10 customers (10 left). Ready within 2 business days. If the Safety Scan finds no problem rated medium or worse, you pay nothing.