Evaluation report
Warningsdeus-agent-runner · mcp704abc9· 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/sliamh11/Deus @ 704abc9 — ★ 48 · Python · MIT · last push 2 days ago
Manifest detected
kind=mcp slug=deus-agent-runner · path=container/agent-runner · source=package.json
Slug is URL-safe
"deus-agent-runner" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/deus-agent-runner
Version is semver
1.0.0
Documentation
4 passed1 warningDescription qualitywarn
Only 5 words · 36 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
19,423 chars · 11 sections · 11 code blocks
Tags / topics declared
8 total — ai-assistant, ai-memory, claude-code, container-isolation, persistent-memory, self-improving-ai (+2)
README has usage / example sections
found: Quick Start · Usage
Homepage / docs URL declared
https://github.com/sliamh11/Deus
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
LICENSE
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 2 days ago
Tests detected
11 test directories · 266 test files
CI configuration detected
GitHub Actions (13 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.