database-migrations — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited database-migrations (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
A schema change touches persistent, shared, irreplaceable data. Slow down: a bad migration can't be "just reverted" once data is lost.
production schema. Each migration is small, ordered, version-controlled, and has a tested down/rollback path where possible.
that writes BOTH old and new.
This keeps old and new code working simultaneously → zero downtime, safe rollback.
that stops using it — you can't roll back without data loss.
migration on a copy with realistic volume — lock duration and timeouts bite at scale.
migration can be safely retried.
Red flag: an irreversible DROP/ALTER shipped together with the code change, or a backfill that locks a big table in a single statement.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.