Evaluation report
Warningsagent-dashboard · mcp8f87ce1· 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/hoangsonww/Claude-Code-Agent-Monitor @ 8f87ce1 — ★ 789 · TypeScript · MIT · last push today
Manifest detected
kind=mcp slug=agent-dashboard · source=package.json
Slug is URL-safe
"agent-dashboard" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/agent-dashboard
Version is semver
1.3.0
Documentation
5 passedDescription quality
8 words · 59 chars — OK but more detail helps
README is present and substantial
180,882 chars · 29 sections · 43 code blocks
Tags / topics declared
35 total — claude, claude-code, anthropic, agent, dashboard, real-time (+29)
README has usage / example sections
found: Quick Start · Example
Homepage / docs URL declared
https://github.com/hoangsonww/Claude-Code-Agent-Monitor#readme
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
13 high/critical advisories — [email protected] (HIGH: GHSA-5528-5vmv-3xc2) · [email protected] (HIGH: GHSA-72gw-mp4g-v24j) (+11)
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
2 passed2 warningsMCP: @modelcontextprotocol/sdk in dependencieswarn
No @modelcontextprotocol/sdk dependency declared
Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.
MCP: ESM packagewarn
package.json missing "type": "module"
Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.
MCP: launch path
bin: ccam · scripts.start
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
12 test directories · 69 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.