Resilience risk scan
Availability risk shows up in the PR, with a score and evidence
The risk scan assesses each service with what the platform records about it: Compute applications, the dependency and ownership graph, SLOs, incidents from the last 30 days and configuration findings. Each rule ends in one of four states (failed, passed, no data, not applicable), and the result is a score, the coverage and the blast radius across the services that depend on it.
The PR check asks the same question before merge: it reads the PR's Dockerfile, docker compose, Kubernetes manifests and simple Terraform and flags only the new risks it introduces. Below the workspace minimum score, the check blocks the pipeline.
How it works
- Risks read in the PR: a single replica, missing probes, missing memory limit, unpinned image, database without Multi-AZ, without backup or without deletion protection.
- Score = max(0, 100 − sum of weights), with critical 25, high 15, medium 8 and low 3. In the per-service scan, the weight grows with criticality and with dependents.
- Only new risks count: what was already in the base (same rule, same resource) is listed separately and does not lower the score.
- Suppression by rule and path, with a justification and an expiry of up to 90 days. A suppressed risk leaves the score and stays listed.
- Workspace minimum score defaults to 60. Zero never blocks, and only admins can change it.
- The response returns the rule, file and line, resource and recommendation for each new risk.
export AIUBY_TOKEN=... # key with resilience:check
aiuby resilience check --repo acme/checkout --ref "$GITHUB_HEAD_REF" --base main
aiuby resilience check Dockerfile k8s/app.yaml --base origin/main # local files; base via git showWhat it does not do
- The scan is text-based: Helm, Kustomize and Terraform modules are not resolved.
- An unrecognized file type becomes a note in the response, never "approved".
- A rule with no data neither lowers the score nor counts as passed: a high score with low coverage means little was checked.
- It does not call your cloud, inject faults or generate load. The check accepts up to 50 files per call.