Evaluation report

• Repository is reachable

  https://github.com/tercumantanumut/selene @ 8ada9d2 — ★ 169 · TypeScript · MIT · last push yesterday

• Manifest detected

  kind=mcp slug=selene · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/selene

• Version is semver

  0.3.5

• Description qualitywarn

  Only 6 words · 32 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README has usage / example sectionswarn

  README has no Usage / Example / Quick start / Installation heading at any level

  Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.

• README is present and substantial

  10,430 chars · 10 sections · 2 code blocks

• Tags / topics declared

  17 total — agent, antigravity, codebase-indexing, codex, deferred-loading, diffusion-models (+11)

• Homepage / docs URL declared

  https://selene.engineer

• Dependencies: known vulnerabilitieswarn

  1 high/critical advisory — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7)

  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.25.2"

• MCP: SDK version pinned

  pinned at "^1.25.2"

• MCP: server surface

  0 tools

• 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 yesterday

• Tests detected

  16 test directories · 333 test files

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.