Evaluation report
Warnings@jeffreycao/copilot-api · mcp1a171da· 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/caozhiyuan/copilot-api @ 1a171da — ★ 906 · TypeScript · MIT · last push today
Manifest detected
kind=mcp slug=jeffreycao-copilot-api · source=package.json
Slug is URL-safe
"jeffreycao-copilot-api" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/jeffreycao-copilot-api
Version is semver
1.13.24
Documentation
5 passedDescription quality
12 words · 93 chars — OK but more detail helps
README is present and substantial
46,964 chars · 22 sections · 26 code blocks
Tags / topics declared
5 total — github-copilot, codex, ai-gateway, multi-provider, anthropic-compatible
README has usage / example sections
found: Installation · Usage · Usage (+2)
Homepage / docs URL declared
https://github.com/caozhiyuan/copilot-api
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
9 high/critical advisories — [email protected] (HIGH: GHSA-3vhc-576x-3qv4) · [email protected] (HIGH: GHSA-88fw-hqm2-52qc) (+7)
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: copilot-api · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.29.0"
MCP: SDK version pinned
pinned at "^1.29.0"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
2 test directories · 46 test files
CI configuration detected
GitHub Actions (5 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.