0
/ 100
Polished and well engineered. Punching above its star count.
Free, open-source time keeping for live events
Documentation
80
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 Other.
Engineering
85
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.
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (apps/client/src/common/components/view-params-editor/__tests__).
CI is configured (.github/workflows/build_cli.yml).
Linter or formatter configured (devDependency in package.json).
Project health
100
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)
- 110Forks
- 181Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 904Watchers
Responsiveness
- 2d 12hMedian issue response
- <1hMedian PR merge time
- 40Open issues
Repository files23 root entries
- .githubGood: CI is configured (.github/workflows/build_cli.yml).
- appsGood: Test files detected (apps/client/src/common/components/view-params-editor/__tests__).
- e2e
- packages
- .deepsource.toml
- .dockerignore
- .gitignoreGood: .gitignore present.
- .nvmrc
- .oxfmtrc.json
- .oxlintrc.json
- DEVELOPMENT.md
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSE.mdGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.ts
- 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.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.
- SPONSOR.md
- tsconfig.common.json
- turbo.json
- vitest.workspace.js