Strong early engineering with some momentum.
Maintain beautiful, version-controlled documentation alongside your Laravel codebase. Markdown in, a polished docs site out.
Documentation
94
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
71
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.
No dependency lockfile found (−70 pts).
→ Commit composer.lock so Composer installs are repeatable.
Test files detected (phpunit.xml).
CI is configured (.github/workflows/tests.yml).
PHP linting configured (phpstan.neon).
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)
- 1Forks
- 13Releaseslatest 6d ago
Community
- —Community health
- —authors own >50% of commits
- 76Watchers
Responsiveness
- 3d 2hMedian issue response
- <1hMedian PR merge time
- 14Open issues
Repository files28 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).Good: Dependabot covers 2 ecosystems (composer, npm). Dependencies stay current.
- config
- docs
- resources
- src
- stubs
- tests
- .gitattributes
- .gitignoreGood: .gitignore present.
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- composer.jsonGood: Dependency manifest found (composer.json).
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.Good: Contributing guide includes code examples.
- crowdin.yml
- LICENSE.mdGood: Licensed under MIT.
- package.json
- phpstan.neonGood: PHP linting configured (phpstan.neon).
- phpunit.xmlGood: Test files detected (phpunit.xml).
- pint.json
- playwright.config.ts
- 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.
- rector.php
- SECURITY.mdGood: Security policy present.
- sonar-project.properties
- sponsor.config.ts
- sponsors.png
- sponsors.svg
- testbench.yaml