It has a clear README, tests, release notes, and an MIT license. The tiny project has no security policy, and its workflow uses two unpinned actions. Its stable version and lack of deprecation help, but maintenance appears to have stopped.
58%
Total Score
75
100
88
67
The package has 5 releases but none in the last 12 months; its latest release was about 20 months ago. This indicates a meaningful maintenance concern for a dependency, though the release history is not wholly absent.
There were 0 commits and 0 active maintainers in the last 3 months, consistent with the roughly 20-month release gap. This materially raises the risk that compatibility fixes may not arrive.
Composer build tooling is present, but no security scanning tools were detected. For a small PHPStan extension this is a modest transparency and maintenance gap, not evidence of unsafe behavior.
The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented, although the small scope limits the severity of this gap.
The single workflow was fully analyzed, uses read-only permissions, and has no reported audit findings or untrusted triggers. However, both of its 2 action references are unpinned, leaving avoidable dependency drift risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
phpstan/phpstan 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.