Saved report · free to view

← Scan another repository

DEPLOYMENT REPORT

vercel/nextjs-subscription-payments

OVERALL RESULT1 issue to fix
YOUR NEXT MOVE · CONFIRMED FINDING1 / 3

Environment variables

utils/stripe/client.ts:8

Add NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE= (empty) to .env.example; set the value privately in Vercel.

Why this first?

Confirmed source findings come before review items, using this scan only. No code is changed automatically. Rescan after making changes.

What was checked? · 4 categories

Scanned: Next.js, Deployment, Env, Supabase

Ignored: Prisma/DB

ENV

Fail
CHECK 04Breaks at runtime

Environment variables

3 env variables are missing from .env.example: NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE, NEXT_PUBLIC_VERCEL_URL, STRIPE_SECRET_KEY_LIVE.

Why it works locally: Locally next dev reads your .env.local, which is never pushed. Vercel only has the variables you add under Project Settings, and NEXT_PUBLIC_ values are fixed at build time.
Show evidence (3)
  • ↳ NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE → missing from committed env template
  • ↳ NEXT_PUBLIC_VERCEL_URL → missing from committed env template
  • ↳ STRIPE_SECRET_KEY_LIVE → missing from committed env template
Suggested fix: Add empty lines to .env.example in the repository root: NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE= + NEXT_PUBLIC_VERCEL_URL= + STRIPE_SECRET_KEY_LIVE=; push the file.

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 (4)
Launch checklist and scan limitations

Review the findings and coverage before launch. Runtime behavior and checkout were not tested.

Return to findings and available fixes ↑

Manual verification · not completed

Not verified

Checks performed

Did DeployDoctor solve it?

Come back after your next deploy and tell us. One click, no account.

Your next step

Exact files and steps are free. Copy them and apply the changes in your repository.

Get notified about new findings

Know when your next deploy is at risk

DeployDoctor rescans vercel/nextjs-subscription-payments once a day and emails you when something new breaks. Free, no account.

One email only when a scan finds something new, and every email has an unsubscribe link.

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.

DeployDoctor: 1 issue to fix[![DeployDoctor](https://deploydoctor.nyttolabs.com/r/506218a9-4fe1-4d91-9a8e-39b71992125a/badge)](https://deploydoctor.nyttolabs.com/r/506218a9-4fe1-4d91-9a8e-39b71992125a)

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 →[![DeployDoctor repo status](https://deploydoctor.nyttolabs.com/badge/vercel/nextjs-subscription-payments.svg)](https://deploydoctor.nyttolabs.com/score/vercel/nextjs-subscription-payments)

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.

Scan with DeployDoctor[![Scan with DeployDoctor](https://deploydoctor.nyttolabs.com/badge.svg)](https://deploydoctor.nyttolabs.com/vercel/nextjs-subscription-payments)