0
/ 100
Strong community interest, but tests, CI, or docs need work.
AVRDUDE is a utility to program AVR microcontrollers
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 GPL-2.0.
Engineering
26
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/build.yml).
Linter or formatter configured (.editorconfig).
Project health
68
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.
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)
- 190Forks
- 6Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 1,142Watchers
Responsiveness
- <1hMedian issue response
- 1d 11hMedian PR merge time
- 18Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).
- src
- supporting-docs
- tools
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- AUTHORS
- avrdude.pdf
- build.sh
- CMakeLists.txt
- CMakeSettings.json
- COPYING
- INSTALL
- NEWS
- 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.