Evaluation report
Warningsvoltagent-example-with-cerbos · mcp0d8c7f9· 3 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/VoltAgent/voltagent @ 0d8c7f9 — ★ 10,016 · TypeScript · MIT · last push today
Manifest detected
kind=mcp slug=voltagent-example-with-cerbos · path=examples/with-cerbos · source=package.json
Slug is URL-safe
"voltagent-example-with-cerbos" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/voltagent-example-with-cerbos
Version is semver
0.1.0
Documentation
4 passed1 warningDescription qualitywarn
Only 3 words · 40 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
19,919 chars · 7 sections · 5 code blocks
Tags / topics declared
24 total — agent, ai, authorization, cerbos, voltagent, agents (+18)
README has usage / example sections
found: Example
Homepage / docs URL declared
https://voltagent.dev
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
3 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+1)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE file at repo root
LICENCE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
5 passedMCP: launch path
scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.12.1"
MCP: SDK version pinned
pinned at "^1.12.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
2 test directories · 220 test files
CI configuration detected
GitHub Actions (3 workflows)
Behavioral
This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.