why — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited why (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 a single specific package — "why is [email protected] flagged?", "where does brace-expansion come from?", "is requests actually exploitable?":
scan_project with the workspace path (or use the most recent .tridentchain-out/scan-report.json if available).raw_summary.affected_components, find the entry matching the package name and version.[email protected] (npm))raw_summary.scan_coverage.by_source for the manifest, then read the lockfile to identify the parent that pulled it in). Show the dep chain: your-app → [email protected] → [email protected].cd <project> && npm install minimatch@latest).tridentchain-security --scan project --project-path . --output-dir .tridentchain-out
# Then jq into the report:
jq '.affected_components[] | select(.name == "lodash")' .tridentchain-out/scan-report.jsonnpm audit fix --force without explicit user consent — it can introduce breaking changes.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.