Evaluation report
Passingdomscribe · pluginc3959ea· 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/patchorbit/domscribe @ c3959ea — ★ 173 · TypeScript · MIT · last push 3 weeks ago
Manifest detected
kind=plugin slug=domscribe · source=.claude-plugin/plugin.json
Slug is URL-safe
"domscribe" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/domscribe
Version is semver
0.5.2
Documentation
5 passedDescription quality
29 words · 192 chars — "Domscribe is a pixel-to-code development tool that maps running UI elements to t…"
README is present and substantial
21,329 chars · 9 sections · 16 code blocks
Tags / topics declared
20 total — ai, claude-code-plugin, copilot-cli-plugin, cursor-plugin, developer-tools, devtools (+14)
README has usage / example sections
found: Getting Started
Homepage / docs URL declared
https://github.com/patchorbit/domscribe
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
Plugin: manifest location
manifest at .claude-plugin/plugin.json (modern convention)
Maintenance
3 passedRecent activity
last push 3 weeks ago
Tests detected
124 test files
CI configuration detected
GitHub Actions (2 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.