Popular for its size, but the engineering basics lag behind the interest.
High-performance, streaming/chunking Java LZF codec, compatible with standard C LZF package
Documentation
58
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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/main.yml).
Test files detected (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)
- 44Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 258Watchers
Responsiveness
- 7hMedian issue response
- 4hMedian PR merge time
- 6Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Dependabot configured for github-actions.
- .mvn
- srcGood: Test files detected (src/test).
- testdata
- .gitattributes
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under Other.
- mvnw
- pom.xmlGood: Dependency manifest found (pom.xml).
- profile-comp-perf
- profile-skip
- profile-uncomp-perf
- 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.
- run-comp-perf
- run-skip
- run-uncomp-perf
- VERSION.txt