0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Facial authentication for Linux
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (84).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
26
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/ci.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Project health
86
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 1Forks
- 1Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 78Watchers
Responsiveness
- 12hMedian issue response
- 1hMedian PR merge time
- 3Open issues
Repository files26 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docsGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- gaze
- gaze-cli
- gaze-core
- gaze-gui
- gnome-shell-extension
- packaging
- pam-gaze
- pam-gaze-core
- pam-gaze-grosshack
- scripts
- .gitignoreGood: .gitignore present.
- AGENTS.md
- bun.lock
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- GEMINI.md
- Justfile
- LICENSEGood: Licensed under MIT.
- mise.tomlGood: Environment pinned via mise.toml.
- package.json
- README.mdGood: 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.
- renovate.json
- wrangler.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/gundulabs/gaze)