Evaluation report
Warningsreins · plugind5bc85d· 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/pegasi-ai/reins @ d5bc85d — ★ 408 · Python · Apache-2.0 · last push 4 weeks ago
Manifest detected
kind=plugin slug=reins · source=.claude-plugin/plugin.json
Slug is URL-safe
"reins" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/reins
Version is semver
0.0.13
Documentation
5 passedDescription quality
15 words · 107 chars — "Security controls for AI agents — deterministic policy enforcement, OWASP ASI10 …"
README is present and substantial
3,355 chars · 8 sections · 2 code blocks
Tags / topics declared
14 total — agent-observability, agent-security, ai-monitoring, ai-safety, audit-trail, browser-automation (+8)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://reins.sh/docs
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 .claude-plugin/plugin.json (modern convention)
Maintenance
2 passed1 warningCI 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 4 weeks ago
Tests detected
1 test directory · 6 test files
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.