Saved report · free to view
← Scan another repositoryDEPLOYMENT REPORT
vercel/commerce
No open findings in the completed checks
This is not a production approval. Test the live app and payment flows separately.
What was checked? · 3 categories
Scanned: Next.js, Deployment, Env
Ignored: Supabase, Prisma/DB
Since the previous scan
Since the previous scan
Previous report from Oct 20, 2026, 8:15 PM UTCNothing changed in the checks both scans ran.
Ran in only one of the two scans, so not compared: Payment and production safety.
No actionable findings in the files checked.
Scan your private code for $2.
A 24-hour pass for public and private repository scans. Private code requires your GitHub authorization. One-time payment, no subscription, nothing renews.
Passed checks and scan coverage (8)
- Next.js entrypointPass
✅ Next.js entrypoint found - no change needed
- Broken importsPass
Every relative and @/ import found resolves to a file in the repository tree.
- Vercel-incompatible server codePass
No Playwright, Puppeteer, SQLite binding, filesystem write in an API route, or Node-only import in Edge code was found.
- Build configurationPass
One lockfile, a build script and a Node version Vercel supports.
- DependenciesPass
Every package the Next.js build imports is declared in package.json, and the lockfile matches it.
- Payment and production safetyPass
No matching production safety risks in the source files checked. This is not a payment or runtime verification.
- Environment variablesPass
Every process.env variable found is documented and no secret-looking value uses NEXT_PUBLIC_.
- Hardcoded secretsPass
No live Stripe, AWS, GitHub or Supabase secret key and no private key was found in the files we read.
Launch checklist and scan limitations
Deployment preflight passed the checks performed. Runtime behavior and checkout were not tested.
Return to findings and available fixes ↑
Manual verification · not completed
- Verify production environment values and authorized callback URLs in your hosting dashboard.
- Run a clean production build and smoke-test the deployed application.
- If payments are used, perform a real end-to-end checkout test, signed webhook delivery and duplicate-event test before advertising.
Not verified
- Static repository analysis only; repository code was not installed, built or executed.
- Runtime behavior, live availability, traffic capacity, inventory and checkout were not tested.
- Hosting environment values, webhook delivery, payment fulfillment and database transactions were not verified.
Checks performed
- Next.js entrypoint: no matching findings
- Broken imports: no matching findings
- Vercel-incompatible server code: no matching findings
- Build configuration: no matching findings
- Dependencies: no matching findings
- Payment and production safety: no matching findings · 3 applicable production rule families evaluated
- Environment variables: no matching findings
- Hardcoded secrets: no matching findings
Did DeployDoctor solve it?
Come back after your next deploy and tell us. One click, no account.
Get notified about new findings
Know when your next deploy is at risk
DeployDoctor rescans vercel/commerce once a day and emails you when something new breaks. Free, no account.
Share report or add to README
README badge
Shows this report's result in your README. It updates when you scan again and paste the new link.
[](https://deploydoctor.nyttolabs.com/r/2d2fbf58-1658-4141-b813-b5ed9d37f84a)Latest repo status in your README
One link follows the latest public scan of the default branch, with its date and commit. Views never start scans.
Open repo status →[](https://deploydoctor.nyttolabs.com/score/vercel/commerce)
Scan button for your README
For templates and starters. The link points at this repository, so someone who forks it changes the owner/repo in the link to scan their own copy before the first deploy.
[](https://deploydoctor.nyttolabs.com/vercel/commerce)