exelban/stats

0

/ 100

Documentation78
Engineering72
Health68
Swift39,786MIT6d ago
Grade a repo

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

macOS system monitor in your menu bar

Documentation

78

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

72

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

CI/CD14pt72

CI is configured (.github/workflows/build.yaml).

Tests18pt80

Test files detected (Tests).

Linting and formatting5pt100

Linter or formatter configured (.swiftlint.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

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 metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Issue or PR templates present.
  • Kit
    Good: Licensed under MIT.
  • LaunchAtLogin
  • Modules
  • SMC
  • Stats
  • Stats.xcodeproj
  • Tests
    Good: Test files detected (Tests).
  • Widgets
  • .gitignore
    Good: .gitignore present.
  • .swiftlint.yml
    Good: Linter or formatter configured (.swiftlint.yml).
  • exportOptions.plist
  • LICENSE
  • Makefile
  • README.md
    Good: 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.