Evaluation report
Warningsplannotator · plugin90bc8f8· 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/backnotprop/plannotator @ 90bc8f8 — ★ 6,385 · TypeScript · Apache-2.0 · last push yesterday
Manifest detected
kind=plugin slug=plannotator · path=apps/droid-plugin/.factory-plugin · source=plugin.json
Slug is URL-safe
"plannotator" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/plannotator
Version is semver
0.19.21
Documentation
5 passedDescription quality
12 words · 90 chars — OK but more detail helps
README is present and substantial
14,147 chars · 11 sections · 20 code blocks
Tags / topics declared
9 total — agents, claude-code, code-review, codex, obsidian, opencode (+3)
README has usage / example sections
no labeled section but 20 code blocks document usage
Homepage / docs URL declared
https://github.com/backnotprop/plannotator
Safety
1 passed1 warningLICENSE file at repo rootwarn
No LICENSE / LICENCE / COPYING / UNLICENSE file (.md/.txt/.rst variants) and no SPDX-License-Identifier header found in common source files
Pick an SPDX license and add a LICENSE file at the repo root, or put an `SPDX-License-Identifier:` comment at the top of your main source file.
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
3 passedRecent activity
last push yesterday
Tests detected
1 test directory · 123 test files
CI configuration detected
GitHub Actions (3 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.