Solid foundation. Invest in docs and CI to grow from here.
Documentation
70
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 is present.
README documents how to install the project.
Licensed under Other.
Engineering
80
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.
Test files detected (python/maze_builder/connectivity_test.py).
Lockfile present (rust/Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Issue or PR templates present.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (rust/Cargo.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 32Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 93Watchers
Responsiveness
- 4hMedian issue response
- 5hMedian PR merge time
- 9Open issues
Repository files30 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .vscode
- cpp
- gfx
- maps
- my-seeds
- palette_smart_exports
- patches
- pythonGood: Test files detected (python/maze_builder/connectivity_test.py).
- rustGood: Lockfile present (rust/Cargo.lock). Installs are reproducible.Good: Dependency manifest found (rust/Cargo.toml).
- scripts
- TitleScreen
- transit-tube-data
- visualizer
- .dockerignore
- .gitignoreGood: .gitignore present.
- .gitmodules
- asar
- docker-compose.yaml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under Other.
- MapRandoSprites
- Mosaic
- MOSAIC_BUILD_ID
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- room_geometry.json
- sm-json-data
- SpriteSomething
- todo.txt