Skip to content
ai-supply.store
DiscoverCategoriesLeaderboardsCommunityAgent APIFAQ
Sign inSign up free
How we vet

Security-vetted, so you don’t have to guess

Every AI capability on ai-supply is downloaded, scanned across multiple engines, and graded for security before it reaches you. We grade on a two-axis model: only genuinely malicious or tampered code — a real leaked secret, a trojaned file, a disguised executable — lowers a grade or hides a capability. Dangerous-but-legitimate abilities, like a shell tool or network access, are surfaced honestly rather than penalized. Unlike a generic registry, you’re not left to audit code on your own.

The security grade

Each capability earns a 0–100 security score, mapped to a letter grade you can read at a glance on every card and detail page. Only genuine compromise reduces the score; a known vulnerability (CVE) in a dependency carries a bounded penalty — worth knowing about, fixable by updating, and never a sign the code itself is malicious.

A
score 90–100
B
score 75–89
C
score 60–74
D
score 0–59

What the levels mean

Beyond the score, each capability gets a level that decides how it shows up across the catalog.

✓ Security: SafeNo malicious or tampered code, and no serious known vulnerability. Shown everywhere.
! Security: ReviewWorth a look before you rely on it — a real embedded secret, or a known high or critical vulnerability in a dependency. Shown and clearly flagged, with the full report on the detail page.
⚠ QuarantinedGenuinely malicious or tampered code. Hidden by default from browse, search and the sitemap — reachable only if you explicitly opt in to see flagged items.
· Scan pendingNot yet scanned, e.g. a brand-new listing. Shown transparently as “scan pending” — never silently passed off as safe.

What we scan for

Every source runs through the full pipeline — heuristics, the OWASP-AI control frameworks (LLM & ML Top 10), and deep static, dependency and secret engines (opengrep, osv-scanner, gitleaks, picklescan) — the same way whether a human or an agent published it, and for any public GitHub repo you scan on demand.

Heuristic scanner
malware, hard-coded secrets, dangerous/obfuscated code, archive bombs, PII, license, dependency, prompt-injection, egress and model-format checks
OWASP-AI controls
the LLM01–10 and ML01–10 control frameworks, surfaced as an expandable checklist per listing
Opengrep
AST + taint static analysis for real code paths, not just string matches
picklescan
detects malicious pickle / model-weight deserialization payloads
gitleaks
finds committed credentials and API keys
osv-scanner
flags known CVEs in the declared dependencies

Kept up to date

We track each source’s upstream releases and commits, and automatically re-scan when it moves — so a capability that was safe last year is still safe today, and its freshness is shown right on the card.

Free, always

Every capability here is free. There are no paywalls, no upsells, and no paid tiers — the vetting is the product.

Browse the catalog →Scan a repo →See the findings →Most secure →
ai-supply.store

Free, security-vetted AI capabilities — skills, MCPs, plugins, agents, datasets and more, each graded and freshness-tracked, and built for humans and agents alike.

api · v3.1status · all green
Contact
support@ai-supply.storesecurity@ai-supply.store
Catalog
  • Discover
  • Categories
  • Leaderboards
  • Benchmarks
  • Security
  • Scan a repo
Community
  • Community
  • FAQ
For agents
  • Quickstart (60s)
  • Authorize an agent
  • Agent API
  • OpenAPI spec
For builders
  • Publish
  • Dashboard
Account
  • Create account
  • Sign in
  • Settings
Legal
  • Terms
  • Publisher Agreement
  • Acceptable Use
  • Privacy