0
/ 100
Rough and inactive. Tests, CI, and a fuller README would revive it.
The CircleCI Android Docker Convenience Image.
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 B (80).
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.
- 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 .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated 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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
42
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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 (.circleci/config.yml).
Issue or PR templates present.
Project health
23
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
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
- -Median PR merge time
- 0Open issues
Repository files40 root entries
- .circleciGood: CI is configured (.circleci/config.yml).
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Issue or PR templates present.
- 2021.08Good: Environment pinned via 2021.08/Dockerfile.
- 2021.09
- 2021.10
- 2021.12
- 2022.01
- 2022.03
- 2022.04
- 2022.06
- 2022.07
- 2022.08
- 2022.09
- 2022.10
- 2022.12
- 2023.02
- 2023.03
- 2023.04
- 2023.05
- 2023.06
- 2023.07
- 2023.08
- 2023.09
- 2023.10
- 2023.11
- 2023.12
- 2024.01
- img
- variants
- .gitmodules
- ALIASES
- androidFeed.sh
- build-images.sh
- Dockerfile.template
- GEN-CHECK
- LICENSEGood: Licensed under MIT.
- manifest
- push-images.sh
- 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.
- shared
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/johnnyb/cimg-android)