0
/ 100
Strong community interest, but tests, CI, or docs need work.
An offline macOS music player
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 (83).
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
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 MIT.
Engineering
43
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 Package.resolved for application projects so Swift Package Manager resolves the same versions.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.swiftlint.yml).
Issue or PR templates present.
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)
- 65Forks
- 26Releaseslatest 11mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,527Watchers
Responsiveness
- 15hMedian issue response
- <1hMedian PR merge time
- 30Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .vscode
- Application
- Configuration
- Core
- docs
- Managers
- Models
- Petrichor.xcodeproj
- Resources
- Scripts
- Utilities
- Views
- .gitignoreGood: .gitignore present.
- .swiftlint.ymlGood: Linter or formatter configured (.swiftlint.yml).
- ACKNOWLEDGEMENTS.md
- LICENSEGood: Licensed under MIT.
- PetrichorApp.swift
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kushalpandya/petrichor)