jordanbaird/ice

0

/ 100

Swift28,516GPL-3.09mo ago
Grade a repo

Strong community interest, but docs and engineering haven't caught up to the hype.

Powerful menu bar manager for macOS

Documentation

82

Contributing guide5pt5

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

43

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

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/lint.yml).

Linting and formatting5pt100

Linter or formatter configured (.swiftlint.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

53

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.

Activity5pt40

Last pushed 6-12 months ago (−60 pts).

A recent commit signals the project is still maintained.

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Issue or PR templates present.
  • Ice
  • Ice.xcodeproj
  • Resources
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .swiftlint.yml
    Good: Linter or formatter configured (.swiftlint.yml).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • FREQUENT_ISSUES.md
  • LICENSE
    Good: Licensed under GPL-3.0.
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.