37
/ 100
The fundamentals need work — start with test coverage and CI.
Weather App that pulls information from weeWX
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (72).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
60
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 GPL-3.0.
Engineering
11
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/SWH.yml).
Project health
94
.gitignore present.
Dependency manifest found (build.gradle).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 70 / 125Commits (30d / 90d)
- 10Forks
- 297Releaseslatest 8y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 28Watchers
Responsiveness
- 6hMedian issue response
- 16hMedian PR merge time
- 0Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/SWH.yml).
- .ideaIssue: Build artifacts or local files may be committed (.idea/appInsightsSettings.xml) (−40 pts).Fix: Remove them and add to .gitignore.
- app
- fastlane
- fdroid-submission
- gradle
- screenshots
- scripts
- .gitignoreGood: .gitignore present.
- build.gradleGood: Dependency manifest found (build.gradle).
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under GPL-3.0.
- local.properties
- 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.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.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.
- settings.gradle
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/evilbunny2008/weewxweatherapp)