supply-chain-scan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited supply-chain-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 about dependency vulnerabilities, CVEs, supply-chain risk, IDE extension security, or wants to audit package.json / lockfiles / requirements.txt:
.tridentchain-out under the project unless the user specifies another path.output_paths.epss_remediation_html for the prioritised view.raw_summary.intelligence_sources.sources_used.kev), call them out separately — these are actively exploited in the wild.tridentchain-security --scan project --project-path <workspace> --output-dir .tridentchain-out
# Or for full system coverage:
tridentchain-security --scan all --project-path <workspace> --output-dir .tridentchain-outRead .tridentchain-out/scan-report.json for the full data; scan-remediation-epss.html for the prioritised remediation queue.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.