0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Route ACARS/VDLM2 messages between various services
Documentation
50
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 MIT.
Engineering
67
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/lint.yaml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (rust/libraries/acars_connection_manager/tests).
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)
- 5Forks
- 27Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 18Watchers
Responsiveness
- 9hMedian issue response
- 3hMedian PR merge time
- 7Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/lint.yaml).
- acars_router
- rootfs
- rustGood: Test files detected (rust/libraries/acars_connection_manager/tests).
- .dictionary.txt
- .dockerignore
- .envrc
- .gitignoreGood: .gitignore present.
- acars_router_audit.md
- BUILD.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- DockerfileGood: Environment pinned via Dockerfile.
- flake.lock
- flake.nix
- LICENSEGood: Licensed under MIT.
- pre-commit-hooks.MD
- 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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- renovate.json