56
/ 100
Early-stage engineering. The fastest wins are test coverage and CI.
A collaborative list of awesome Swift libraries and resources. Feel free to contribute!
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 (82).
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 a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
88
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Licensed under CC0-1.0.
Engineering
18
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 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.
No dependency lockfile found (−70 pts).
→ Commit Gemfile.lock so Bundler installs are repeatable.
CI is configured (.github/workflows/merge.yml).
Project health
100
Dependency manifest found (.github/check-swift-version/package.json).
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)
- 3,139Forks
- 0Releases
Community
- 85% - GoodCommunity health
- -authors own >50% of commits
- 26,189Watchers
Responsiveness
- <1hMedian issue response
- 1hMedian PR merge time
- 5Open issues
Repository files11 root entries
- .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: CI is configured (.github/workflows/merge.yml).Good: Dependency manifest found (.github/check-swift-version/package.json).
- .gitignoreGood: .gitignore present.
- .ruby-versionGood: Environment pinned via .ruby-version.
- ab-results-contents.json-filtered.json
- ab-results-contents.json-markdown-table.json
- ab-results-contents.json.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- contents.json
- Dangerfile
- LICENSEGood: Licensed under CC0-1.0.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/matteocrippa/awesome-swift)