Evaluation report
Warningssmolagents · mcp526069c· 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
"1.27.0.dev0" 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/huggingface/smolagents @ 526069c — ★ 28,234 · Python · Apache-2.0 · last push 2 weeks ago
Manifest detected
kind=mcp slug=smolagents · source=pyproject.toml
Slug is URL-safe
"smolagents" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/smolagents
Documentation
4 passed1 warningTags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Description quality
18 words · 114 chars — "🤗 smolagents: a barebones library for agents. Agents write python code to call …"
README is present and substantial
14,111 chars · 8 sections · 15 code blocks
README has usage / example sections
no labeled section but 15 code blocks document usage
Homepage / docs URL declared
https://huggingface.co/docs/smolagents
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
4 passedMCP: launch path
launch declared in pyproject.toml
MCP: @modelcontextprotocol/sdk in dependencies
non-Node server (pyproject.toml) — uses its language's MCP SDK
MCP: ESM package
non-Node server (pyproject.toml) — n/a
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 2 weeks ago
Tests detected
1 test directory · 23 test files
CI configuration detected
GitHub Actions (6 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.