swiftlang/swift

0

/ 100

Documentation83
Engineering52
Health100
Swift70,057Apache-2.05d ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

The Swift Programming Language

Documentation

83

README12pt70

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

52

CI/CD14pt0

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.

Tests18pt80

Test files detected (SwiftCompilerSources/Sources/Optimizer/Utilities/Test.swift).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (SwiftCompilerSources/Package.swift).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files33 root entries
  • .github
    Good: Issue or PR templates present.
  • apinotes
  • benchmark
  • bindings
  • cmake
  • docs
  • include
  • lib
  • localization
  • Runtimes
  • stdlib
  • SwiftCompilerSources
    Good: 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
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .flake8
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • Brewfile
  • CHANGELOG.md
  • CMakeLists.txt
  • CODE_OWNERS.TXT
  • CONTRIBUTING.md
    Good: 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.txt
    Good: Licensed under Apache-2.0.
  • README.md
    Good: 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.