Evaluation report
Warningsmatryoshka-rlm · mcpccf3ca0· 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/yogthos/Matryoshka @ ccf3ca0 — ★ 142 · TypeScript · Apache-2.0 · last push 5 weeks ago
Manifest detected
kind=mcp slug=matryoshka-rlm · source=package.json
Slug is URL-safe
"matryoshka-rlm" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/matryoshka-rlm
Version is semver
0.2.39
Documentation
5 passedDescription quality
11 words · 76 chars — OK but more detail helps
README is present and substantial
28,131 chars · 11 sections · 38 code blocks
Tags / topics declared
11 total — llm, rlm, mcp, claude, document-analysis, recursive (+5)
README has usage / example sections
found: Installation · Usage
Homepage / docs URL declared
https://github.com/yogthos/Matryoshka#readme
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
2 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE 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
5 passedMCP: launch path
bin: rlm, rlm-mcp, lattice-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.0.0"
MCP: SDK version pinned
pinned at "^1.0.0"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 5 weeks ago
Tests detected
1 test directory · 164 test files
CI configuration detected
GitHub Actions (1 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.