rollback-readiness — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited rollback-readiness (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Part of shipsafe — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine.
python3 scripts/readiness.py <project_root> [--json]Runs 8 weighted checks and emits PASS/WARN/FAIL per check plus a 0–100 readiness score: health endpoint exists · env documented in .env.example · lockfile committed · migrations reversible · no committed secrets (quick pass) · runtime version pinned · deploy CI has concurrency control · README has run/deploy instructions.
Score bands: ≥80 ready · 60–79 fix FAILs first · <60 deploying now means debugging in production.
This skill is the entry point to the rest of the pack — each FAIL maps to a deeper skill (secrets → secret-preflight, migrations → migration-reversibility, env → env-drift, CI → ci-workflow-doctor). Run the deep skill on whatever fails, fix, and rerun until the score clears 80.
The framing to give the user: the score measures whether the person paged at 2am — possibly future-you — can understand, redeploy, and roll back this project without you in the room.
Exit codes: 0 score ≥ 80, 1 below.
All paths below are relative to this skill's directory (rollback-readiness/).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.