A well-known project done right. Strong docs and solid engineering throughout.
Documentation
91
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
90
Test files detected (phpunit.xml).
Lockfile present (composer.lock). Installs are reproducible.
CI is configured (.github/workflows/build.yaml).
PHP linting configured (.editorconfig).
Issue or PR templates present.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (composer.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 289Forks
- 34Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 2,125Watchers
Responsiveness
- 2d 14hMedian issue response
- 15hMedian PR merge time
- 19Open issues
Repository files41 root entries
- .githubGood: CI is configured (.github/workflows/build.yaml).Good: Issue or PR templates present.
- app
- bootstrap
- config
- database
- docker
- lang
- plugins
- public
- resources
- routes
- storage
- tests
- .dockerignore
- .editorconfigGood: PHP linting configured (.editorconfig).
- .env.example
- .gitignoreGood: .gitignore present.
- .prettierrc.json
- artisan
- bounties.md
- compose-bind.yml
- compose-full-stack.yml
- compose.yml
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- contributing.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- contributor_license_agreement.md
- crowdin.yml
- DockerfileGood: Environment pinned via Dockerfile.
- Dockerfile.base
- Dockerfile.dev
- licenseGood: Licensed under AGPL-3.0.
- package-lock.json
- package.json
- phpstan.neon
- phpunit.xmlGood: Test files detected (phpunit.xml).
- pint.json
- 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.
- security.mdGood: Security policy present.
- vite.config.js
- yarn.lock