0
/ 100
Popular and well-maintained. A little polish away from elite status.
The Swift Programming Language
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.
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
83
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
52
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No dependency lockfile found (−70 pts).
→ Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.
Test files detected (SwiftCompilerSources/Sources/Optimizer/Utilities/Test.swift).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (SwiftCompilerSources/Package.swift).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository files33 root entries
- .githubGood: Issue or PR templates present.
- apinotes
- benchmark
- bindings
- cmake
- docs
- include
- lib
- localization
- Runtimes
- stdlib
- SwiftCompilerSourcesGood: Test files detected (SwiftCompilerSources/Sources/Optimizer/Utilities/Test.swift).Good: Dependency manifest found (SwiftCompilerSources/Package.swift).
- test
- tools
- unittests
- userdocs
- utils
- validation-test
- .clang-format
- .clang-tidy
- .dir-locals.el
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .flake8
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mailmap
- Brewfile
- CHANGELOG.md
- CMakeLists.txt
- CODE_OWNERS.TXT
- 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.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSE.txtGood: Licensed under Apache-2.0.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/swiftlang/swift)