Skill Scanner
Security Scanner for Agent Skills
Is Skill Scanner safe? Strong public trust posture, backed by multiple independent signals.
Compare Skill Scanner
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Skill Scanner scores 82.6/100 (Grade A), ranked #15 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 97% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Skill Scanner compares in Agent Skills
- #13 Antigravity Sdk Python 82.9 +0.3
- #14 Claudecodeui 82.7 +0.1
- #15 Skill Scanner 82.6 this agent
- #16 DSH Better Sidebar 82.5 −0.1
- #17 Modlens 80.9 −1.7
Bars show each HVTrust score; the tick marks Skill Scanner’s 82.6.
Where the 82.6 comes from
HVTrust dimensions vs the Agent Skills average
82.6 / 100 · 100.0% confidenceSkill Scanner Agent Skills average (351 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
71.0 / 100Supply Chain Trust
Common questions about Skill Scanner
Does Skill Scanner publish package provenance?
Does Skill Scanner have an OpenSSF Scorecard?
Is Skill Scanner actively maintained?
What license does Skill Scanner use?
Are Skill Scanner's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Skill Scanner's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Skill Scanner?
For maintainers
HVTrust scores Skill Scanner from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/skill-scanner)
<a href="https://hvtracker.net/agents/skill-scanner"><img src="https://hvtracker.net/badge/skill-scanner.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON