66
/ 100
Popular for its size, but the engineering basics lag behind the interest.
[MIRROR] Alpine packages build scripts
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 A (97).
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.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
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
56
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
CONTRIBUTING guide found.
A license file is present.
Engineering
60
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
Lockfile present (community/anki/yarn.lock). Installs are reproducible.
CI is configured (.gitlab-ci.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (community/easypki/go.mod).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 938 / 4698Commits (30d / 90d)
- 706Forks
- 0Releases
Community
- 50% - FairCommunity health
- 6 bus factorauthors own >50% of commits
- 719Watchers
Responsiveness
- -Median issue response
- 7hMedian PR merge time
- 1Open issues
Repository files15 root entries
- .githooks
- .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.
- .gitlab
- communityGood: A license file is present.Good: Lockfile present (community/anki/yarn.lock). Installs are reproducible.Good: Dependency manifest found (community/easypki/go.mod).
- main
- scripts
- testing
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- .mailmap
- CODINGSTYLE.md
- COMMITSTYLE.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/alpinelinux/aports)