official-stockfish/fishtest
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

The Stockfish testing framework

Documentation55
Engineering69
Health93
Python340today

Documentation

55

License6pt0

No license detected.

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

Install and run instructions9pt45

README documents how to install the project.

README12pt70

README is present.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

69

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.

Reproducibility6pt70

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

CI/CD14pt72

CI is configured (.github/workflows/lint.yaml).

Tests18pt80

Test files detected (server/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

93

Dependency manifest6pt79

Dependency manifest found (pyproject.toml).

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)
  • 155
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 340
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 14h
    Median PR merge time
  • 114
    Open issues
Repository files12 root entries
  • .github
    Good: CI is configured (.github/workflows/lint.yaml).
  • docs
  • server
    Good: Test files detected (server/tests).
  • worker
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • AUTHORS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.