0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Unofficial Java API library of CHZZK (치지직, the video streaming service of Naver)
Documentation
56
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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 is present.
Licensed under MIT.
Engineering
49
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/gradle-publish.yml).
Test files detected (src/test).
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)
- 12Forks
- 15Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 45Watchers
Responsiveness
- 6hMedian issue response
- 1hMedian PR merge time
- 1Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/gradle-publish.yml).
- docs
- gradle
- image
- srcGood: Test files detected (src/test).
- .gitbook.yaml
- .gitignoreGood: .gitignore present.
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- env.properties.example
- gradle.properties
- gradlew
- gradlew.bat
- jitpack.yml
- LICENSEGood: Licensed under MIT.
- publish.properties.example
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- settings.gradle.kts