0
/ 100
Solid engineering. The main gap is visibility.
Android App which handles the information about temple. People can register for poojas and keep a track of all donations made to the temple.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
82
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 MIT.
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 (app/src/androidTest/java/org/amfoss/templeapp/ApplicationTest.java).
CI is configured (.travis.yml).
Issue or PR templates present.
Project health
75
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Dependency manifest found (build.gradle).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files13 root entries
- .githubGood: Issue or PR templates present.
- appGood: Test files detected (app/src/androidTest/java/org/amfoss/templeapp/ApplicationTest.java).
- gradle
- .gitignoreGood: .gitignore present.
- .travis.ymlGood: CI is configured (.travis.yml).
- build.gradleGood: Dependency manifest found (build.gradle).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under MIT.
- 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.Good: README documents how to install the project.Good: README documents how to run 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/abhinandhari/templeapp)