Good community traction and solid fundamentals. Nearly in the top tier.
Go middlewares for HTTP servers & proxies
Documentation
47
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under Apache-2.0.
Engineering
85
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.
Lockfile present (go.sum). Installs are reproducible.
Test files detected (buffer/buffer_test.go).
CI is configured (.github/workflows/go-cross.yml).
Formatting enforced (.golangci.yml).
Project health
100
Dependency manifest found (go.mod).
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)
- 331Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 2,106Watchers
Responsiveness
- 4d 23hMedian issue response
- 3hMedian PR merge time
- 32Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/go-cross.yml).
- bufferGood: Test files detected (buffer/buffer_test.go).
- cbreaker
- connlimit
- forward
- internal
- memmetrics
- ratelimit
- roundrobin
- stream
- testutils
- trace
- utils
- .gitignoreGood: .gitignore present.
- .golangci.ymlGood: Formatting enforced (.golangci.yml).
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- README.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.