0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
OpenSource Backup and restore your entire Termux environment across devices.
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 (88).
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 `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
97
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under MIT.
Engineering
35
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 configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/ci.yml).
Issue or PR templates present.
Project health
91
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 1Forks
- 6Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 27Watchers
Responsiveness
- -Median issue response
- 20hMedian PR merge time
- 0Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- src
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- DISCLAIMER.md
- FAQ.md
- GOVERNANCE.md
- install.sh
- LICENSEGood: Licensed under MIT.
- PRIVACY.md
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.
- SECURITY.mdGood: Security policy present.
- termux-sync.py
- tsctl
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/djunekz/termux-sync)