0
/ 100
Solid engineering. The main gap is visibility.
E-commerce server with both monolithic and microservices versions
Documentation
82
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
57
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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 (cmd/server/server_test/server_test.go).
Formatting enforced (gofmt (built into Go toolchain)).
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)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- 2hMedian issue response
- 3hMedian PR merge time
- 1Open issues
Repository files15 root entries
- api
- cmdGood: Test files detected (cmd/server/server_test/server_test.go).
- internal
- pkg
- .dockerignore
- .gitignoreGood: .gitignore present.
- config_example.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- Makefile
- prometheus_example.yml
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.