My personal configuration for PHPStan
72%
Total Score
50
100
89
67
The registry namespace and repository owner match, but both are a single user account. This is consistent ownership, though it offers less continuity than organization backing.
All two commits in the last 3 months came from one contributor, leaving maintenance dependent on a single person. The repository is user-owned rather than organization-backed, so there is no provided organizational handoff signal to compensate for this concentration.
The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these low adoption indicators provide little external validation.
Composer is used as a build tool, but no security scanning tools were detected. This is a modest transparency and supply-chain hygiene gap, not evidence that the package is unsafe.
No repository security policy was found, reducing the documented path for reporting vulnerabilities. This is a documentation gap for a small configuration package rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpstan/phpstan Version ^2.0 | — | — |
phpstan/phpstan-strict-rules Version ^2.0 | — | — |
phpstan/phpstan-deprecation-rules Version ^2.0 | — | — |
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.