Solid engineering. The main gap is visibility.
https://songrank.dev - Rank your favorite artists' tracks.
Documentation
57
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under MIT.
Engineering
74
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 (phpunit.xml).
Lockfile present (composer.lock). Installs are reproducible.
CI is configured (.github/workflows/tests.yml).
PHP linting configured (.editorconfig).
Project health
100
Dependency manifest found (composer.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
- 15 / 29Commits (30d / 90d)
- 3Forks
- —Releases
Community
- 42% - WeakCommunity health
- —authors own >50% of commits
- 9Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 2Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).
- app
- bootstrap
- config
- database
- lang
- public
- resources
- routes
- storage
- tests
- .editorconfigGood: PHP linting configured (.editorconfig).
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- artisan
- CLAUDE.md
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- package-lock.json
- package.json
- phpunit.xmlGood: Test files detected (phpunit.xml).
- postcss.config.js
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- vite.config.js