Evaluation report
Warningscanvas-apps-tools · pluginb371d02· 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/ToluVictor/canvas-apps-tools @ b371d02 — ★ 108 · MIT · last push 3 months ago
Manifest detected
kind=plugin slug=canvas-apps-tools · source=.claude-plugin/plugin.json
Slug is URL-safe
"canvas-apps-tools" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/canvas-apps-tools
Version is semver
1.0.2
Documentation
5 passedDescription quality
12 words · 71 chars — OK but more detail helps
README is present and substantial
4,983 chars · 9 sections · 6 code blocks
Tags / topics declared
7 total — canvas-apps, claude-code, claude-code-plugin, claude-code-skills, power-apps, power-platform (+1)
README has usage / example sections
found: Installation · Usage
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
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
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 3 months ago
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.