Is quick-scan safe to install?

SaferSkills independently audited quick-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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/tridentchain-security/skills/quick-scan/SKILL.md · 1 file

plugins/tridentchain-security/skills/quick-scan/SKILL.md1.3 KB · Markdown

description: Fast cached-only scan of project dependencies for high-severity CVEs. Uses the local advisory cache without making fresh network calls — sub-second for most projects. Use when the user wants a pre-commit check, a fast pulse on supply-chain risk, or is offline. For thorough live-advisory checks use `scan` or `supply-chain-scan` instead.

Quick scan

When the user asks for a fast, quick, or pre-commit dependency check, or says they're offline:

Call the tridentchain MCP tool scan_project with:

project_path = workspace root (absolute)
output_dir = .tridentchain-out
run_profile = "quick" ← important: cached advisories only, no live fetch
max_findings = 20 (keep summaries tight)

Report only HIGH and CRITICAL findings by default; the user asked for a fast pulse, not a full triage.
If the cache is empty (no prior scan), tell the user explicitly and offer a scan (full live) run instead.

CLI fallback

tridentchain-security --scan project --run-profile quick --project-path . --output-dir .tridentchain-out

When NOT to use quick-scan

User wants the most up-to-date data → use scan (live advisory fetch)
User wants system packages or IDE extensions → use scan-full
User wants to confirm a fix landed → use validate-fixes

quick-scan— agent skill

Is quick-scan safe to install?

Quick scan

CLI fallback

When NOT to use quick-scan

Audit the pieces. Scan the whole. Decide.