Strong setup for a brand-new repo. Docs and CI already in good shape.

Eval framework that ranks agentic coding frameworks (Superpowers, Compound Engineering, Agent Skills, GSD) by having each build the same spec with the same harness+model in isolated sandboxes, graded on a weighted evidence-based rubric: PRD adherence, code quality, speed, token spend

Documentation

62

License6pt0

No license detected.

Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

68

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt40

CI is configured (.github/workflows/pages.yml).

Reproducibility6pt80

Lockfile present (bun.lock). Installs are reproducible.

Tests18pt100

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 7
    Watchers

Responsiveness

  • Median issue response
  • <1h
    Median PR merge time
  • 4
    Open issues
Repository files25 root entries
  • .cursor
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/pages.yml).
  • config
  • designs
  • docs
  • infra
    Good: Environment pinned via infra/trial-image/Dockerfile.
  • openspec
  • pages
  • scripts
  • src
  • targets
  • tests
    Good: Test files detected (tests).
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CLAUDE.md
  • package.json
    Good: Dependency manifest found (package.json).
  • PROMPT_OPEN_SWE.md
  • PROMPT.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • ROADMAP.md
  • tsconfig.json