Good shape overall. A few tweaks would push it into the top tier.
⏰ The open-source time tracking app for individuals.
Documentation
88
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
61
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.
Test files detected (apps/web/config/next-auth.test.ts).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/lint.yml).
Linter or formatter configured (.editorconfig).
Project health
89
Dependency manifest found (package.json).
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)
- 35Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 258Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 14Open issues
Repository files23 root entries
- .githubGood: CI is configured (.github/workflows/lint.yml).
- .husky
- .vscode
- appsGood: Test files detected (apps/web/config/next-auth.test.ts).
- docs
- packages
- .cursorignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .lintstagedrc.json
- .nvmrc
- .prettierignore
- .secretlintrc.json
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- eslint.config.mjs
- LICENSEGood: Licensed under AGPL-3.0.
- logo.svg
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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
- turbo.json