75
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
78
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under CC-BY-4.0.
Engineering
80
No dependency lockfile found (−70 pts).
→ Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.
Test files detected (PulseLoopTests/ActivityServiceTests.swift).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.swiftlint.yml).
Issue or PR templates present.
Project health
53
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.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 39 / 39Commits (30d / 90d)
- 30Forks
- 0Releases
Community
- 71% - FairCommunity health
- -authors own >50% of commits
- 237Watchers
Responsiveness
- 21hMedian issue response
- 1d 1hMedian PR merge time
- 13Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- docs
- PulseLoop
- PulseLoop.xcodeproj
- PulseLoopLiveActivity
- PulseLoopTestsGood: Test files detected (PulseLoopTests/ActivityServiceTests.swift).
- screenshots
- .gitignoreGood: .gitignore present.
- .swiftlint.ymlGood: Linter or formatter configured (.swiftlint.yml).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.
- icon-source.svg
- LICENSEGood: Licensed under CC-BY-4.0.
- PulseLoopLiveActivityExtension.entitlements
- 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.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.Good: README documents how to install the project.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/saksham2001/pulseloopios)