Your code. Your deployment platform.

Cloudflare Workers and Pages

Configuration: wrangler.toml, wrangler.json, wrangler.jsonc

Configuration syntax, recorded compatibility dates, Worker entrypoint paths, source-backed Node compatibility risks, duplicate bindings, mixed Pages/Workers configuration and assets paths.

Not verified: Generated entrypoints need build verification. Assets-only Workers do not require main. Node compatibility defaults depend on the recorded date. Dashboard bindings, secrets and deployed behavior are not verified.

Netlify

Configuration: netlify.toml

Build base paths, literal package-manager scripts including contexts and nested packages, functions inside publish directories, forced SPA rewrite ordering, self-redirect risks and invalid edge-function path declarations.

Not verified: Dashboard overrides, plugins, generated redirects and edge functions are not executed. Hosting environment values and the final publish output remain unverified.

Vercel

Configuration: vercel.json and supported framework configuration

Existing build, import, environment, dependency, Next.js, Vite, SvelteKit, Astro, function and cron checks remain available.

Not verified: A static result is not a production build, runtime test or confirmation that payment fulfillment works.

Railway and Docker

Configuration: Legacy railway.json / railway.toml, Dockerfile

Legacy Railway config syntax and Dockerfile path risks; explicit environment-file copies into Docker image layers.

Not verified: Railway TypeScript IaC is recognized but not evaluated. Service root settings, current configuration eligibility, container builds, image vulnerabilities and persistent volumes are not verified.

Language support means different checks

• JavaScript and TypeScript: syntax-tree import analysis and supported build, dependency, environment, payment and production-safety patterns. It does not run the compiler or tests.
• Rust: Cargo edition/minimum-version consistency, pinned toolchain, explicit target paths and locked-build configuration. No compilation or crate audit.
• Python and Go: recognized manifests, limited literal environment-reference checks and known secret patterns. No interpreter, compiler or dependency audit.
• Other detected languages: file inventory and applicable known secret/configuration checks. Detection is not a claim of full language analysis.

One scanner, the same limits

These checks feed the existing report, Launch Readiness, PR comparisons, API, CLI and GitHub Action. One free repository scan per day per IP on the website; existing passes and private-repository permissions still apply. No additional AI calls are used for platform checks.

The legacy API category vercel means Build & deployment. Its name is retained for compatibility; it does not restrict the analysis to Vercel.

Repository code is never installed, imported or executed. Partial scans remain labeled, and no result guarantees a successful deployment.