Instant scan.
Replace github.com with scanaislop.com on any public repo URL and get a live aislop score, usually in seconds.
The URL hack
Take any GitHub URL like github.com/scanaislop/aislop and swap the host:
github.com/<owner>/<repo> → scanaislop.com/<owner>/<repo>
No account. No install. No CLI. You land on a page that runs a real scan against the default branch's HEAD commit. Most results arrive in seconds; larger repositories or a busy queue can take a few minutes.
What you see
- The 0–100 score, colour-coded green / amber / red.
- Error and warning counts, plus scan duration.
- The first 20 issues with rule, file:line, severity, and message.
- A copy-ready badge snippet for your README.
- Links to scan another public repo, view workspace plans, or add a README badge.
How fast
Most public repositories finish in 5–15 seconds end-to-end:
- Same commit and scanner version · instant. The page renders the cached scan immediately.
- First visit · ~1s to fetch the repo metadata, ~5–10s to clone and run the engines.
- Large repository · may take a few minutes. Anything over 250 MB is rejected up-front.
What runs
Same deterministic engines as aislop scan on your laptop, with no LLM at runtime. The worker clones the repository, and optional dependency checks may query package registries:
as any, swallowed errors, console leftovers, generic names.Limits
- Public repos only. Private or inaccessible repos are rejected. If you own one, sign in and connect it through the GitHub App.
- Repo size cap of 250 MB on GitHub's reported repository size. Larger repos return a friendly error.
- Five new scans per minute per client. Cached results and job polling have separate limits.
- Shared queue protection. When the queue is full, cached results remain available and new scans ask you to retry in a minute.
- Default branch only. Sign in to scan a specific branch, PR, or commit.
Move into a workspace
The instant-scan flow uses a shared public workspace. A paid workspace adds:
- Private branch and PR scans via the GitHub App.
- PR check runs and inline annotations.
- Standards hierarchy (org → team → project) and the visual rules manager.
- Per-team dashboards and shared scan history.
Embed the score
Once a public scan exists, the badge service renders it for free. Drop this in your README:
[](https://scanaislop.com/<owner>/<repo>)
See Public badges for the full spec, score bands, and caching layers.