Is your CI healthy? Scan any GitHub repo.
Paste a public GitHub repo and see in seconds what is failing, what is flaky or slow, and a 0 to 100 health score. No account.
Each chip: health score out of 100 · CI pass rate % · GEL checks passed. Green is good, red needs a look.
Trend
One point per hourly snapshot, whole org.
Red now
Workflows whose newest completed run on the default branch failed or timed out. The strip is the last 20 runs, oldest left.
Per repo
Runs per day for the last 14 days (green passed, red failed), pass rate of the last 100 runs and median run time. Red repos first.
Flaky
Workflows that went from pass to fail or back at least three times in their last 100 runs, with no change in between that we can see. Most flips on top.
Slow
The slowest workflows by median run time. The dashed outline is the 90th percentile run.
Outcomes
Runs per day on default branches, and how every run in the window ended.
OSS score
How well each repo is run as open source, 0 to 100: licence, README, CONTRIBUTING, SECURITY, code of conduct, a description with topics, CI that exists and CI that is green. Lowest first, so the gaps are on top.
AI-SDLC
Is each repo ready for coding agents, and do deterministic checks hold the harness together? Instructions, specs, tools, guardrails and verification, after Anthropic's AI-SDLC guidance. Repo flags are read from each repo's root folder; the harness checks appear when a scoreboard is supplied (Flisk's own run does).
GEL guards
Guards from flisk-sh/gel run on each repo's workflow files. A live scan runs two of them in your browser, the real GEL code, no copy.
5-second test
Can a stranger on a phone tell what each site is for in five seconds? GEL's five-second-test guard reads the first screen: a short headline, a short lead in plain words, and a button. Worst first.
Scoreboard
Deterministic checks the account's own CI runs, published with the snapshot. Gates and ratchets fail CI; reports only inform.