Good shape overall. A few tweaks would push it into the top tier.
Example microservices showing how to use Kafka and Kafka Streams with Spring Boot on the example of distributed transactions implementations with the SAGA pattern
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 GPL-3.0.
Engineering
59
No Java/Kotlin linter configured.
→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Test files detected (order-service/src/test).
CI is configured (.circleci/config.yml).
Project health
100
Dependency manifest found (pom.xml).
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)
- 212Forks
- 0Releases
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 415Watchers
Responsiveness
- 22hMedian issue response
- 4hMedian PR merge time
- 3Open issues
Repository files14 root entries
- .circleciGood: CI is configured (.circleci/config.yml).
- base-domain
- order-serviceGood: Test files detected (order-service/src/test).
- payment-service
- stock-service
- .gitignoreGood: .gitignore present.
- ANALYSIS_AND_RECOMMENDATIONS.md
- arch.png
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- LICENSE.mdGood: Licensed under GPL-3.0.
- pom.xmlGood: Dependency manifest found (pom.xml).
- 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.
- renovate.json
- scenario.png