83
/ 100
Solid engineering. The biggest lever is CI.
Helps to download binaries from release assets
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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
88
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
66
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/build-phar-release.yml).
Test files detected (tests).
Lockfile present (composer.lock). Installs are reproducible.
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
- 18 / 30Commits (30d / 90d)
- 2Forks
- 45Releaseslatest 1y ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 104Watchers
Responsiveness
- 21hMedian issue response
- <1hMedian PR merge time
- 16Open issues
Repository files31 root entries
- .githubGood: CI is configured (.github/workflows/build-phar-release.yml).
- .phive
- bin
- resources
- skills
- src
- testsGood: Test files detected (tests).
- .editorconfigGood: PHP linting configured (.editorconfig).
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .php-cs-fixer.dist.php
- box.json.dist
- CHANGELOG.md
- CLAUDE.md
- composer-require-checker.json
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- context.yaml
- dload.xml
- dload.xsd
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSE.mdGood: Licensed under BSD-3-Clause.
- Makefile
- psalm-baseline.xml
- psalm.xml
- README-es.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.
- README-ru.md
- README-zh.md
- README.md
- 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-internal/dload)