0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Stanford Spezi template for building apps on Apple Platforms
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 C (73).
See your top fixesTop 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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 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
67
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
60
No dependency lockfile found (−70 pts).
→ Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.
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-and-test.yml).
Test files detected (TemplateApplicationTests/TemplateApplicationTests.swift).
Linter or formatter configured (.swiftlint.yml).
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)
- 42Forks
- 19Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 137Watchers
Responsiveness
- 19d 13hMedian issue response
- 17hMedian PR merge time
- 12Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/build-and-test.yml).
- fastlane
- firebase
- LICENSES
- Scripts
- TemplateApplication
- TemplateApplication.xcodeproj
- TemplateApplicationTestsGood: Test files detected (TemplateApplicationTests/TemplateApplicationTests.swift).
- TemplateApplicationUITests
- .gitignoreGood: .gitignore present.
- .linkspector.yml
- .periphery.yml
- .swiftlint.ymlGood: Linter or formatter configured (.swiftlint.yml).
- CITATION.cff
- codecov.yml
- CONTRIBUTORS.md
- LICENSE.mdGood: Licensed under MIT.
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- REUSE.toml
- TemplateApplication.xctestplan
- TemplateApplication.xctestplan.license
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/stanfordspezi/spezitemplateapplication)