0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
a diffusion-based ML model for generating osu! maps from raw audio
Documentation
82
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
22
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
Lockfile present (uv.lock). Installs are reproducible.
Issue or PR templates present.
Project health
93
Dependency manifest found (pyproject.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)
- 13Forks
- 20Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 144Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 5Open issues
Repository files11 root entries
- .githubGood: Issue or PR templates present.
- .vscode
- osu_dreamer
- windows_scripts
- .gitignoreGood: .gitignore present.
- .python-version
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.