Evaluation report
Warningsxuanlin-overmind · pluginb212ae1· 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
4 passed1 warningVersion is semverwarn
"v4" doesn't match MAJOR.MINOR.PATCH
Use semver — e.g. `0.1.0`, `1.2.3-beta.1`. The CLI sorts updates by semver.
Repository is reachable
https://github.com/xuanlinAI/overmind @ b212ae1 — ★ 83 · JavaScript · MIT · last push 5 weeks ago
Manifest detected
kind=plugin slug=xuanlin-overmind · source=plugin.json
Slug is URL-safe
"xuanlin-overmind" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/xuanlin-overmind
Documentation
5 passedDescription quality
39 words · 48 chars — "CC 的外挂认知引擎 — 66 模块 · 5 层记忆 · 知识图谱推理 · 红队审查 · 自进化"
README is present and substantial
14,377 chars · 17 sections · 4 code blocks
Tags / topics declared
15 total — ai-agent, ai-memory, codex, deepseek, hermes, knowledge-graph (+9)
README has usage / example sections
found: Installation
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
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
3 passed1 warningPlugin: bundled artifacts presentwarn
Couldn't find a skills/ subdir or an MCP server config inside the plugin
A plugin is most useful when it bundles ≥ 1 skill or an MCP server.
Plugin: manifest fields complete
Plugin: bundle shape
3 hooks
Plugin: manifest location
manifest at plugin.json
Maintenance
2 passed1 warningTests detectedwarn
no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files
Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.
Recent activity
last push 5 weeks ago
CI configuration detected
GitHub Actions (1 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.