dns-cutover — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dns-cutover (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.
Two modes:
# 1) What records do I need?
python3 scripts/dns_cutover.py plan <domain> <platform>
# 2) Are my records right? (paste zone export or `dig +noall +answer` output into a file)
python3 scripts/dns_cutover.py check <domain> <platform> <records_file> [--json]Platforms: vercel, netlify, cloudflare-pages, github-pages.
check validates apex and www records, and additionally catches the three classic cutover mistakes:
Process to walk the user through: lower TTL to 300s the day BEFORE → run plan → set records → export/dig the records into a file → run check → only then flip. After cutover, verify HTTPS on BOTH apex and www — cert issuance is the step that fails silently.
Some values are project-specific (e.g. <yoursite>.netlify.app); the script marks these and the user's dashboard value wins.
Exit codes: 0 ok, 1 problems found.
All paths below are relative to this skill's directory (dns-cutover/).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.