Evaluation report

• Repository is reachable

  https://github.com/glincker/stacklit @ 6aa0176 — ★ 100 · Go · MIT · last push 2 months ago

• Manifest detected

  kind=mcp slug=stacklit · path=npm · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/stacklit

• Version is semver

  0.3.1

• Description quality

  20 words · 145 chars — "Zero-config codebase context for AI agents. One command generates a ~250-token n…"

• README is present and substantial

  11,349 chars · 17 sections · 18 code blocks

• Tags / topics declared

  27 total — ai, codebase, index, agent, mcp, cli (+21)

• README has usage / example sections

  no labeled section but 18 code blocks document usage

• Homepage / docs URL declared

  https://github.com/glincker/stacklit

• 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: @modelcontextprotocol/sdk in dependencieswarn

  No @modelcontextprotocol/sdk dependency declared

  Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.

• 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

  bin: stacklit

• MCP: server surface

  0 tools

• Recent activity

  last push 2 months ago

• Tests detected

  18 test files

• CI configuration detected

  GitHub Actions (3 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.