73
/ 100
Solid engineering. The biggest lever is a reproducible setup.
The Testing Framework
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Commit composer.lock so Composer installs are repeatable.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
80
README documents how to install the project.
CONTRIBUTING guide found.
README is present.
Licensed under BSD-3-Clause.
Engineering
68
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.
Test files detected (bridge/double/tests).
CI is configured (.github/workflows/tests.yml).
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)
- 21Forks
- 234Releaseslatest 9mo ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 222Watchers
Responsiveness
- 5d 22hMedian issue response
- <1hMedian PR merge time
- 35Open issues
Repository files24 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: 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.
- bin
- bridgeGood: Test files detected (bridge/double/tests).
- core
- docs
- internal
- plugin
- resources
- skills
- tests
- tools
- .editorconfigGood: PHP linting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CHANGELOG.md
- codecov.yml
- composer.jsonGood: Dependency manifest found (composer.json).
- infection.json
- LICENSE.mdGood: Licensed under BSD-3-Clause.
- 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
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/php-testo/testo)