validate-fixes — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited validate-fixes (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.
When the user upgrades dependencies or asks to confirm a fix:
scan_project or scan_full on project_path (MCP) or: tridentchain-security --scan project --project-path <path> --output-dir .tridentchain-outSave the JSON summary or scan-report.json as baseline if the output dir will be overwritten.
npm update, pip install -U, etc.).project_path.validate_after_patch with baseline_json and after_patch_json (full tool result strings) tridentchain-security --validate \
--baseline-report <baseline.json> \
--after-report .tridentchain-out/scan-report.jsonresolved_count, remaining_count, new_count, validation_passed.tridentchain-security>=0.1.1 and tridentchain-mcp for MCP pathtridentchain-security==0.1.0 only supports manual JSON comparison (no --validate)Run tridentchain-security twice, then --validate with two report paths. See docs/CAPABILITIES.md.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.