0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
The Testing Framework
Documentation
69
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 BSD-3-Clause.
Engineering
60
No dependency lockfile found (−70 pts).
→ Commit composer.lock so Composer installs are repeatable.
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.
CI is configured (.github/workflows/tests.yml).
Test files detected (bridge/symfony-console/tests).
PHP linting configured (.editorconfig).
Project health
94
.gitignore present.
Dependency manifest found (composer.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 10Forks
- 129Releaseslatest 5mo ago
Community
- -Community health
- -authors own >50% of commits
- 194Watchers
Responsiveness
- 5d 22hMedian issue response
- <1hMedian PR merge time
- 17Open issues
Repository files28 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).
- .ideaIssue: Build artifacts or local files may be committed (.idea/icon.svg) (−40 pts).Fix: Remove them and add to .gitignore.
- bridgeGood: Test files detected (bridge/symfony-console/tests).
- core
- docs
- internal
- plugin
- resources
- skills
- tests
- .editorconfigGood: PHP linting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .php-cs-fixer.dist.php
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- codecov.yml
- composer.jsonGood: Dependency manifest found (composer.json).
- dload.xml
- infection.json
- LICENSE.mdGood: Licensed under BSD-3-Clause.
- mago.toml
- psalm-baseline.xml
- psalm.xml
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- skills.json
- testo.php