Evaluation report
Passingchrome-devtools-mcp · plugin58ba174· 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/ChromeDevTools/chrome-devtools-mcp @ 58ba174 — ★ 46,612 · TypeScript · Apache-2.0 · last push today
Manifest detected
kind=plugin slug=chrome-devtools-mcp · source=.claude-plugin/plugin.json
Slug is URL-safe
"chrome-devtools-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/chrome-devtools-mcp
Version is semver
1.5.0
Documentation
5 passedDescription quality
14 words · 111 chars — OK but more detail helps
README is present and substantial
38,861 chars · 12 sections · 35 code blocks
Tags / topics declared
8 total — browser, chrome, chrome-devtools, debugging, devtools, mcp (+2)
README has usage / example sections
found: Getting started
Homepage / docs URL declared
https://npmjs.org/package/chrome-devtools-mcp
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
6 skills
Plugin: bundle shape
6 skills
Plugin: manifest location
manifest at .claude-plugin/plugin.json (modern convention)
Maintenance
3 passedRecent activity
last push today
Tests detected
1 test directory · 54 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.