Good shape overall. A few tweaks would push it into the top tier.
Spring Boot Starter for Logback-access.
Documentation
68
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under Apache-2.0.
Engineering
70
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.
Test files detected (logback-access-spring-boot-starter/src/test).
CI is configured (.github/workflows/build.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (build.gradle.kts).
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)
- 33Forks
- 66Releaseslatest 9y ago
Community
- —Community health
- —authors own >50% of commits
- 205Watchers
Responsiveness
- 5d 20hMedian issue response
- <1hMedian PR merge time
- 13Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot covers 2 ecosystems (github-actions, gradle). Dependencies stay current.Good: Issue or PR templates present.
- config
- examples
- gradle
- logback-access-spring-boot-starterGood: Test files detected (logback-access-spring-boot-starter/src/test).
- .gitignoreGood: .gitignore present.
- .tool-versionsGood: Environment pinned via .tool-versions.
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Good: Contributing guide includes setup/install instructions.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.Good: Contributing guide includes code examples.
- gradle.properties
- gradlew
- gradlew.bat
- LICENSE.txtGood: Licensed under Apache-2.0.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- settings.gradle.kts