Popular for its size, but the engineering basics lag behind the interest.
Play Mega Man Battle Network online with rollback netcode!
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 AGPL-3.0.
Engineering
30
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/release.yaml).
Lockfile present (Cargo.lock). Installs are reproducible.
Rust linting configured (rustfmt.toml).
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)
- 21Forks
- 225Releaseslatest 4y ago
Community
- —Community health
- —authors own >50% of commits
- 100Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 21Open issues
Repository files31 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/release.yaml).
- bps
- datachannel-wrapper
- discord-ipc
- getgud
- libdatachannel
- linux
- macos
- mgba
- rennet
- tango
- tango-dataview
- tango-filesync
- tango-gamesupport
- tango-pvp
- tango-signaling
- tools
- win
- .gitignoreGood: .gitignore present.
- .gitmodules
- about.toml
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CREDITS.md
- crowdin.yml
- deny.toml
- gamesupport
- LICENSEGood: Licensed under AGPL-3.0.
- 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.
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml).