0
/ 100
Strong community interest, but tests, CI, or docs need work.
Logic-less and semantic Mustache templates with Java
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 Other.
Engineering
47
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.
CI is configured (.github/workflows/build-matrix.yml).
Test files detected (handlebars-caffeine/src/test).
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)
- 387Forks
- 13Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 1,557Watchers
Responsiveness
- 1hMedian issue response
- 1d 1hMedian PR merge time
- 140Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build-matrix.yml).Good: Dependabot configured for maven.
- handlebars
- handlebars-caffeineGood: Test files detected (handlebars-caffeine/src/test).
- handlebars-guava-cache
- handlebars-helpers
- handlebars-jackson
- handlebars-maven-plugin
- handlebars-maven-plugin-tests
- handlebars-springmvc
- src
- tests
- .gitignoreGood: .gitignore present.
- .gitmodules
- LICENSEGood: Licensed under Other.
- 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.
- TODO