Popular for its size, but the engineering basics lag behind the interest.
Lichess local development using Docker Compose.
Documentation
82
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.
README documents how to install the project.
README is present.
Licensed under AGPL-3.0.
Engineering
38
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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.
Lockfile present (command/Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/build.yml).
Project health
100
Dependency manifest found (command/Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 103Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 121Watchers
Responsiveness
- 2hMedian issue response
- 2hMedian PR merge time
- 7Open issues
Repository files22 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/build.yml).
- .vscode
- commandGood: Lockfile present (command/Cargo.lock). Installs are reproducible.Good: Dependency manifest found (command/Cargo.toml).
- conf
- docker
- docs
- quick
- scripts
- static
- .dockerignore
- .gitignoreGood: .gitignore present.
- compose-lila-ws-build.yml
- compose-lila-ws-image.yml
- compose-search.yml
- compose.ymlGood: Environment pinned via compose.yml.
- LICENSEGood: Licensed under AGPL-3.0.
- lichess.code-workspace
- lila-docker
- lila-docker.ps1
- pull-all
- README.mdGood: 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.