Evaluation report

• Repository is reachable

  https://github.com/Robotti-io/copilot-security-instructions @ dc2248d — ★ 42 · JavaScript · Apache-2.0 · last push 7 weeks ago

• Manifest detected

  kind=mcp slug=copilot-instructions-mcp · source=package.json

• Slug is URL-safe

  "copilot-instructions-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/copilot-instructions-mcp

• Version is semver

  1.0.0

• Description quality

  19 words · 124 chars — "A collection os security focused prompts and instructions paired with an mcp ser…"

• README is present and substantial

  16,801 chars · 9 sections · 5 code blocks

• Tags / topics declared

  19 total — robotti, mcp, modelcontext, framework, emotional-sync, rvct (+13)

• README has usage / example sections

  no labeled section but 5 code blocks document usage

• Homepage / docs URL declared

  no homepage declared (registry will use the repo URL) — info-only, not blocking

• Dependencies: known vulnerabilitieswarn

  5 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+3)

  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: ESM packagewarn

  package.json missing "type": "module"

  Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.

• MCP: launch path

  scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.17.2"

• MCP: SDK version pinned

  pinned at "^1.17.2"

• MCP: server surface

  0 tools

• Tests 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.

• Recent activity

  last push 7 weeks ago

• CI configuration detected

  GitHub Actions (1 workflows) · GitLab CI

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.