Evaluation report
Warningsoverkill · plugin60c7bbb· 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/santiago-vargas-de-kruijf/claude-overkill @ 60c7bbb — ★ 13 · MIT · last push 6 weeks ago
Manifest detected
kind=plugin slug=overkill · path=plugins/overkill/.claude-plugin · source=plugin.json
Slug is URL-safe
"overkill" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/overkill
Version is semver
0.1.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
37 words · 263 chars — "Surfaces advanced data structures, distributed-systems algorithms, niche framewo…"
README is present and substantial
2,407 chars · 3 sections · 4 code blocks
README has usage / example sections
found: Usage
Homepage / docs URL declared
https://github.com/santiago-vargas-de-kruijf/claude-overkill
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
empty bundle
Plugin: manifest location
manifest at plugin.json
Maintenance
1 passed2 warningsTests 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.
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.
Recent activity
last push 6 weeks ago
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.