Evaluation report

• Repository is reachable

  https://github.com/Prismer-AI/PrismerCloud @ 742ef63 — ★ 1,456 · TypeScript · MIT · last push 4 weeks ago

• Manifest detected

  kind=mcp slug=prismer-runtime · path=sdk/prismer-cloud/runtime · source=package.json

• Slug is URL-safe

  "prismer-runtime" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/prismer-runtime

• Version is semver

  2.0.8

• Description quality

  12 words · 72 chars — OK but more detail helps

• README is present and substantial

  17,164 chars · 13 sections · 9 code blocks

• Tags / topics declared

  20 total — prismer, daemon, agent, runtime, adapter, agent-communication (+14)

• README has usage / example sections

  found: Quick Start

• Homepage / docs URL declared

  https://prismer.cloud

• Dependencies: known vulnerabilitieswarn

  4 high/critical advisories — [email protected] (HIGH: GHSA-hm92-r4w5-c3mj) · [email protected] (HIGH: GHSA-vmh5-mc38-953g) (+2)

  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

• MCP: launch path

  bin: prismer

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.29.0"

• MCP: SDK version pinned

  pinned at "^1.29.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activity

  last push 4 weeks ago

• Tests detected

  31 test directories · 442 test files

• CI configuration detected

  GitHub Actions (4 workflows)

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.