WholeStack / Repository readiness
Know before you ship.
Connect GitHub, paste a public repository, or choose a local folder. WholeStack exposes static readiness evidence without pretending that a spec-free scan is a signed ShipGate decision.
Scan a repositoryREADY
BLOCKED
Exact revision · mandatory checks · blocking findings · evidence-bound result
01 / Repository intake
Bring the code.
Personal repositories and organization repositories—including repos owned by the WholeStackAI account—work through the GitHub App installation you select.
Loading repository intake
02 / Assessment anatomy
An assessment is not ShipGate.
Scores help prioritize repairs. They never authorize release. Every material change requires a fresh advisory scan and a separate signed ShipGate run.
The advisory scan found no static blocker.
This is readiness guidance, not a ShipGate release decision or deployment authority.
One or more readiness checks failed.
The report names the blocker, its source, and the fastest path back to a fresh scan.
The scanner could not earn a verdict.
Unreadable, empty, or unsupported input never becomes a reassuring green result.
03 / Continuous readiness
Put honest evidence in the merge path.
Select source
Install on a GitHub account or organization
Connect the GitHub App to the account that owns the code. Your WholeStack login and the repository owner do not need to be the same account.
Active repositories
Checking your CI installations…
The rule
A static scan never earns SHIP. Fix its findings, then run the exact revision through the signed ShipGate pipeline before release.