Free readiness check
The free readiness check at app.scalebop.com/check tells you, without an account, whether ScaleBop can deploy a public GitHub repository to AWS. It’s built for apps from Lovable, Bolt, v0 and similar tools, and works for any public repository.
What it reads
Section titled “What it reads”- The latest commit on the repository’s default branch, downloaded once as a ZIP archive from GitHub. ScaleBop uses no GitHub account or token for this, so it can only read repositories anyone can read.
- Only the app’s source and manifest files (
package.json,requirements.txt, config files and so on), the same files ScaleBop reads when you connect a repository after signing up. Folders such asnode_modulesand build output are skipped. - Repositories over 50 MB are refused.
Private repositories can’t be checked this way. Sign up and connect GitHub to check one.
What it shows
Section titled “What it shows”- The verdict: ready to deploy, needs a few answers, or not supported yet, with the reasons.
- What ScaleBop would deploy: a static site on S3 and CloudFront, or a container on ECS Fargate, and the framework it found.
- Security scan counts: how many common security problems the scan found, by severity and by kind (secrets in code, configuration, browser code, application code).
The result doesn’t show which files or lines the problems are in, or how to fix them. Anyone can open a result, so showing exactly where a public repository is weak would help attackers more than the owner. After you sign up and connect the repository, you see each problem’s file and line, with a prompt to fix it in your AI tool.
What it keeps
Section titled “What it keeps”- The verdict, the reasons, what would deploy and the finding counts, for the commit that was checked.
- No source code. The downloaded files are deleted as soon as the check finishes.
- A one-way hash of the requester’s IP address, used for rate limits and abuse reports. The address itself isn’t stored.
Results are deleted after 180 days. If you sign up from a result and add that repository to ScaleBop, the result is linked to your new project and kept with it. A repository checked again at the same commit shows the saved result instead of running the check again.
Who can see a result
Section titled “Who can see a result”Each result has a page at app.scalebop.com/check/<owner>/<repo> that anyone with the link can open. Result pages tell search engines not to index them.
Limits
Section titled “Limits”Each visitor can run 5 checks an hour and 20 a day, and each repository gets one fresh check every 10 minutes. When many people are checking at once, the check asks you to try again in a few minutes.
Removing a result
Section titled “Removing a result”If you own a repository and want its result removed before the 180 days are up, sign in and send a request through Support & feedback (in the site footer), naming the repository. Making the repository private also stops new checks of it.