scan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited scan (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 asks to scan a project for vulnerabilities, audit package.json / requirements.txt, or check dependency security:
scan_project with:project_path = workspace root (absolute path)output_dir = .tridentchain-outrun_profile = "full" (live advisory fetch — default)max_findings = 50raw_summary.affected_components, ranked by epss_score. These are the actual fix-first list.source: "kev"), tag it clearly — these are actively exploited in the wild.output_paths.epss_remediation_html for the prioritised remediation queue (with copy-paste fix commands).scan vs siblings| Situation | Use |
|---|---|
| User wants project deps only, live data | scan (this) |
| User is in a hurry / offline | quick-scan |
| User says "system", "IDE", "extensions", "machine", "everything" | scan-full |
| User upgraded packages and wants to verify | validate-fixes |
| User wants to drill into ONE package | why |
| User wants a fix recipe | fix-plan |
tridentchain-security --scan project --project-path . --output-dir .tridentchain-out~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.