Evaluation report
Warnings@codemieai/code · mcpac92f9a· 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/codemie-ai/codemie-code @ ac92f9a — ★ 261 · TypeScript · Apache-2.0 · last push today
Manifest detected
kind=mcp slug=codemieai-code · source=package.json
Slug is URL-safe
"codemieai-code" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/codemieai-code
Version is semver
0.9.0
Documentation
5 passedDescription quality
28 words · 196 chars — "Unified AI coding assistant CLI - Manage Claude Code, Gemini & custom agents. Mu…"
README is present and substantial
21,507 chars · 12 sections · 33 code blocks
Tags / topics declared
36 total — ai, artificial-intelligence, coding-assistant, code-generation, cli, command-line (+30)
README has usage / example sections
found: Quick Start · Installation · Installation (+1)
Homepage / docs URL declared
https://github.com/codemie-ai/codemie-code#readme
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
1 high/critical advisory — @langchain/[email protected] (HIGH: GHSA-r399-636x-v7f6)
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
bin: codemie, code, codemie-code
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "2.0.0-alpha.2"
MCP: SDK version pinned
pinned at "2.0.0-alpha.2"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
47 test directories · 195 test files
CI configuration detected
GitHub Actions (2 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.