Evaluation report
Warnings@ast-bro/cli · mcp18430fa· 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/aeroxy/ast-bro @ 18430fa — ★ 215 · Rust · MIT · last push 3 weeks ago
Manifest detected
kind=mcp slug=ast-bro-cli · path=cli-typescript · source=package.json
Slug is URL-safe
"ast-bro-cli" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/ast-bro-cli
Version is semver
3.0.0
Documentation
5 passedDescription quality
12 words · 91 chars — OK but more detail helps
README is present and substantial
32,797 chars · 14 sections · 23 code blocks
Tags / topics declared
13 total — ast-bro, ast-outline, ast, code-outline, tree-sitter, llm (+7)
README has usage / example sections
found: Quick start · Getting started
Homepage / docs URL declared
https://github.com/aeroxy/ast-bro
Safety
2 passedLICENSE 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: ast-bro, ast-outline, sb
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 3 weeks ago
Tests detected
1 test directory
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.