0
/ 100
Well engineered. The main gaps are issue and PR templates and a contributing guide.
PHPStan's source code. This is where development happens. Check https://github.com/phpstan/phpstan for the distribution repository.
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 .env.example listing all required environment variables so contributors know what to set up.
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Issue and PR templates6pt
A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
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
86
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
80
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 (apigen/infra/test).
CI is configured (.github/workflows/build-issue-bot.yml).
PHP linting configured (.editorconfig).
Lockfile present (composer.lock). Installs are reproducible.
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
- 441 / 1269Commits (30d / 90d)
- 589Forks
- 0Releases
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 400Watchers
Responsiveness
- -Median issue response
- 3hMedian PR merge time
- 214Open issues
Repository files38 root entries
- .claude
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/build-issue-bot.yml).Good: Renovate is configured (.github/renovate.json). Dependencies update automatically across every package manager it detects.Good: .gitignore present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/icon.png) (−40 pts).Fix: Remove them and add to .gitignore.
- apigenGood: Test files detected (apigen/infra/test).
- bin
- build
- changelog-generator
- compiler
- conf
- e2e
- issue-bot
- patches
- resources
- src
- stubs
- tests
- tmp
- turbo-ext
- .editorconfigGood: PHP linting configured (.editorconfig).
- .gitattributes
- .gitignore
- .typos.toml
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- Makefile
- phpbench.json
- phpcs.xml
- phpstan-baseline.neon
- phpstan-baseline.php
- phpstan.neon.dist
- phpunit.xml
- preload.php
- 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.
- UPGRADING.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/phpstan/phpstan-src)