Good shape overall. A few tweaks would push it into the top tier.
An easy-to-use framework for large scale recommendation algorithms.
Documentation
73
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Apache-2.0.
Engineering
70
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/buildtest_ci.yml).
Test files detected (data/test).
Lockfile present (requirements.txt). Installs are reproducible.
Linter or formatter configured (.ruff.toml).
Project health
100
Dependency manifest found (requirements.txt).
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)
- 74Forks
- 7Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 399Watchers
Responsiveness
- 18hMedian issue response
- 17hMedian PR merge time
- 14Open issues
Repository files24 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/buildtest_ci.yml).
- dataGood: Test files detected (data/test).
- dockerGood: Environment pinned via docker/Dockerfile.
- docs
- examples
- requirements
- scripts
- tzrec
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .pyre_configuration
- .readthedocs.yaml
- .ruff.tomlGood: Linter or formatter configured (.ruff.toml).
- LICENSEGood: Licensed under Apache-2.0.
- MANIFEST.in
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- requirements-cpu.txt
- requirements-cu126.txt
- requirements-cu129.txt
- requirements-gpu.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- setup.cfg
- setup.py