It is clearly licensed, documented, and has a small dependency surface. One maintainer and no commits in the last three months make long-term support less certain; the missing security policy adds a smaller transparency gap.
66%
Total Score
50
100
88
75
Registry publishing access is held by one maintainer. The matching user-owned repository supports a small project story, but it leaves limited apparent redundancy if that maintainer stops contributing.
The repository is owned by a user rather than an organization, consistent with the single-maintainer profile and offering no organizational support signal.
There were no commits and no active maintainers in the last three months. Although a release occurred at the start of that period, the absence of ongoing commit activity lowers confidence in continued maintenance.
Composer is used as the build tool, but no security scanning tools were detected. For a small PHP formatter this is a transparency and maintenance gap, though not evidence of an unsafe release by itself.
The repository has no security policy. This is a modest disclosure and transparency gap, especially for a package installed into developer environments, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpstan/phpstan Version ^2.0.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.