79
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
A practical lab for building, testing, and evaluating apps with Apple's Foundation Models framework.
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 .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.
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
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.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
68
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.
Test files detected (FoundationLabCore/Tests).
CI is configured (.github/workflows/foundation-lab-testflight.yml).
Linter or formatter configured (.swiftlint.yml).
Project health
100
Dependency manifest found (Package.swift).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 213 / 259Commits (30d / 90d)
- 68Forks
- 5Releaseslatest 1mo ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,132Watchers
Responsiveness
- 9hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files25 root entries
- .afm
- .asc
- .githubGood: CI is configured (.github/workflows/foundation-lab-testflight.yml).
- BookPlaygrounds
- Foundation Lab
- Foundation Lab.icon
- FoundationLab.xcodeproj
- FoundationLabCoreGood: Test files detected (FoundationLabCore/Tests).
- images
- Packages
- skills
- Tools
- .gitignoreGood: .gitignore present.
- .swiftlint-adapter-studio.yml
- .swiftlint-core-cli.yml
- .swiftlint.ymlGood: Linter or formatter configured (.swiftlint.yml).
- Agents.md
- CLAUDE.md
- fmf.md
- LICENSEGood: Licensed under MIT.
- Package.resolved
- Package.swiftGood: Dependency manifest found (Package.swift).
- PRODUCT.md
- 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.Good: README documents how to run the project.
- SampleCode.xcconfig
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/rudrankriyam/foundation-models-framework-lab)