Evaluation report
Warningshappyclaw-agent-runner · mcp3040523· 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/riba2534/happyclaw @ 3040523 — ★ 759 · TypeScript · MIT · last push today
Manifest detected
kind=mcp slug=happyclaw-agent-runner · path=container/agent-runner · source=package.json
Slug is URL-safe
"happyclaw-agent-runner" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/happyclaw-agent-runner
Version is semver
1.0.0
Documentation
4 passed1 warningDescription qualitywarn
Only 5 words · 41 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
24,139 chars · 7 sections · 11 code blocks
Tags / topics declared
5 total — claude-agent-sdk, agent-runner, mcp, happyclaw, openclaw
README has usage / example sections
no labeled section but 11 code blocks document usage
Homepage / docs URL declared
https://happyclaw.cc/
Safety
3 passedDependencies: known vulnerabilities
OSV.dev clean — 0 high/critical across 2 deps
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
3 passed1 warningMCP: @modelcontextprotocol/sdk in dependencieswarn
No @modelcontextprotocol/sdk dependency declared
Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.
MCP: launch path
scripts.start
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
2 passed1 warningCI configuration detectedwarn
no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)
Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.
Recent activity
last push today
Tests detected
1 test directory · 79 test files
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.