Strong community interest, but tests, CI, or docs need work.
Advanced manager and monitor for Apache Tomcat, forked from Lambda Probe
Documentation
72
README documents how to install the project.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under GPL-2.0.
Engineering
46
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.github/workflows/ci.yaml).
Test files detected (psi-probe-core/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)
- 383Forks
- 60Releaseslatest 15y ago
Community
- —Community health
- —authors own >50% of commits
- 1,330Watchers
Responsiveness
- 1611d 9hMedian issue response
- 14hMedian PR merge time
- 78Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/ci.yaml).
- .mvn
- docs
- psi-probe-coreGood: Test files detected (psi-probe-core/src/test).
- psi-probe-rest
- psi-probe-tomcat10
- psi-probe-tomcat11
- psi-probe-web
- src
- .gitattributes
- .gitignoreGood: .gitignore present.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- eclipse-java-google-style.xml
- intellij-java-google-style.xml
- LICENSEGood: Licensed under GPL-2.0.
- LICENSE_HEADER
- mvnw
- mvnw.cmd
- 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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- renovate.json