pipeline-verification — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pipeline-verification (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.
A passing unit test means a unit works. It does not mean the change works, and it does not mean the change didn't break something else. Verify end to end, through the path a user actually exercises, and trace what else the change can reach.
Announce at start: "Verifying end to end, not just unit tests."
"TESTS PASS" / "IT COMPILED" / "CONTAINER STARTED" IS NOT "IT WORKS".
Before declaring done, list what the change can affect:
If you changed a contract, the other side of that contract is in scope.
State exactly what you verified and how, and what you did NOT.
| Thought | Reality |
|---|---|
| "Unit tests are green, so it works" | Units work. The feature and its neighbors are unverified. |
| "It compiled / the container started" | That's a precondition, not verification. Exercise the real path. |
| "The change is local — nothing else is affected" | Trace the blast radius before believing that. |
| "The frontend/consumer probably still works" | You changed a contract; assume nothing across it — check it. |
Pairs with: bardak:verify-the-premise (report observed data, not assumed coverage); invoked by bardak:bugfix-tdd and bardak:blind-review before calling work done.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.