0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A space fleet programming game
Documentation
42
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 GPL-3.0.
Engineering
73
No Rust linting or formatting enforced.
→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.
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 is configured (.github/workflows/check.yml).
Test files detected (shared/simulator/tests).
Lockfile present (Cargo.lock). Installs are reproducible.
Project health
100
Dependency manifest found (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)
- 27Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 326Watchers
Responsiveness
- 6hMedian issue response
- 19hMedian PR merge time
- 7Open issues
Repository files23 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/check.yml).Good: Dependabot covers 2 ecosystems (cargo, cargo). Dependencies stay current.
- .vim
- assets
- bundler
- firebase
- frontend
- scripts
- servicesGood: Environment pinned via services/backend/Dockerfile.
- sharedGood: Test files detected (shared/simulator/tests).
- tools
- .dockerignore
- .gitignoreGood: .gitignore present.
- .watchmanconfig
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.lock.user
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- Cargo.toml.user
- CHANGELOG.md
- LICENSEGood: Licensed under GPL-3.0.
- oort3.code-workspace
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- rust-toolchain.toml