0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Resrv is a booking engine for Statamic.
Documentation
60
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 Other.
Engineering
62
No PHP linter or static analysis tool configured.
→ Add PHP_CodeSniffer (phpcs.xml) for style or PHPStan (phpstan.neon) for static analysis. Run either in CI.
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 (composer.lock). Installs are reproducible.
Test files detected (phpunit.xml).
CI is configured (.github/workflows/tests.yml).
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
- -Commits (30d / 90d)
- 2Forks
- 56Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 15Watchers
Responsiveness
- 6d 10hMedian issue response
- <1hMedian PR merge time
- 9Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).
- config
- database
- docs
- public
- resources
- routes
- src
- tests
- .gitattributes
- .gitignoreGood: .gitignore present.
- AVAILABILITY_COLLECTION.md
- CART-BASED-FLOW.md
- CleanShot 2026-06-10 at 13.38.30@2x.png
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- jsconfig.json
- LICENSE.mdGood: Licensed under Other.
- package-lock.json
- package.json
- phpunit.pgsql.xml
- phpunit.xmlGood: Test files detected (phpunit.xml).
- 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- REPORT.md
- TASKS.md
- UPGRADE_TO_RATES.md
- UPGRADE-PAYMENT-GATEWAYS.md
- vite-frontend-css.config.js
- vite-frontend.config.js
- vite.config.js