Evaluation report
Warningsmcp-browser-use · plugin03e0dad· 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/Saik0s/mcp-browser-use @ 03e0dad — ★ 940 · Python · MIT · last push 4 months ago
Manifest detected
kind=plugin slug=mcp-browser-use · source=.claude-plugin/plugin.json
Slug is URL-safe
"mcp-browser-use" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/mcp-browser-use
Version is semver
0.3.0
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
11 words · 76 chars — OK but more detail helps
README is present and substantial
23,102 chars · 14 sections · 51 code blocks
README has usage / example sections
found: Installation · Usage
Homepage / docs URL declared
https://github.com/browser-use/mcp-browser-use
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 passedPlugin: manifest fields complete
Plugin: bundled artifacts present
1 skill
Plugin: bundle shape
1 skill · 1 hook
Plugin: manifest location
manifest at .claude-plugin/plugin.json (modern convention)
Maintenance
1 passed2 warningsRecent activitywarn
last push 4 months ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
CI 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.
Tests detected
1 test directory · 15 test files
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.