Solid engineering. The main gap is visibility.
Transform your Yii2 applications into high-performance, PSR-compliant powerhouses.
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 Other.
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.dist).
CI is configured (.github/workflows/build.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
- 21 / 29Commits (30d / 90d)
- 2Forks
- —Releases
Community
- 100% - GoodCommunity health
- —authors own >50% of commits
- 5Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot covers 2 ecosystems (github-actions, composer). Dependencies stay current.
- docs
- runtime
- src
- tests
- .coderabbit.yaml
- .editorconfigGood: PHP linting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.json
- .styleci.yml
- .stylelintignore
- CHANGELOG.md
- composer-require-checker.json
- composer.jsonGood: Dependency manifest found (composer.json).
- ecs.php
- infection.json5
- LICENSEGood: Licensed under Other.
- phpstan.neon
- phpunit.xml.distGood: Test files detected (phpunit.xml.dist).
- 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
- UPGRADE.md