Polished and well engineered. Punching above its star count.
BGP implemented in the Rust Programming Language
Documentation
78
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 Apache-2.0.
Engineering
88
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.
Test files detected (packet/tests).
CI is configured (.github/workflows/build.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Lockfile present (packet/tests/fixtures/gen/go.sum). 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)
- 63Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 585Watchers
Responsiveness
- 21hMedian issue response
- <1hMedian PR merge time
- 4Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot covers 2 ecosystems (cargo, gomod). Dependencies stay current.
- api
- config
- daemon
- docs
- kernel
- packetGood: Test files detected (packet/tests).Good: Lockfile present (packet/tests/fixtures/gen/go.sum). Installs are reproducible.
- table
- testsGood: Environment pinned via tests/e2e/add-path/docker-compose.yml.
- tools
- .dockerignore
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- BUILD.md
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CODEOWNERS
- DESIGN.md
- LICENSEGood: Licensed under Apache-2.0.
- 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.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.