jaywcjlove/awesome-mac

0

/ 100

Documentation87
Engineering25
Health100
Swift105,983CC0-1.06d ago
Grade a repo

Massive community, but the engineering fundamentals haven't kept pace with the star count.

 This project is dedicated to collecting high-quality macOS software and organizing them systematically by different categories for easy search and use.

Documentation

87

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under CC0-1.0.

Engineering

25

Tests18pt0

No tests detected anywhere in the repository.

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

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

CI/CD14pt40

CI is configured (.github/workflows/ci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files26 root entries
  • .codex
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • build
  • dist
  • docs
    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.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • feed
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
  • command-line-apps-ja.md
  • command-line-apps-ko.md
  • command-line-apps-zh.md
  • command-line-apps.md
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • editor-plugin-ja.md
  • editor-plugin-zh.md
  • editor-plugin.md
  • idoc.yml
  • LICENSE
    Good: Licensed under CC0-1.0.
  • logo.svg
  • package.json
    Good: Dependency manifest found (package.json).
  • README-ja.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • README-ko.md
  • README-zh.md
  • README.md
  • renovate.json