Custom PHPStan rules and extensions for EsfahanAhan.
62%
Total Score
caution
A brand-new package has little maintenance history, with broad workflow permissions and all actions unpinned.
The package was first released less than a day ago and has only three releases, so there is not yet enough history to demonstrate sustained maintenance.
There were no commits and no active maintainers in the measured three-month window. Because the project is less than a day old, this mainly reflects limited history, but it still leaves maintenance capacity unproven.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest repository-hygiene gap.
The repository has no security policy. This is a transparency gap, though the small and very new project provides limited history in which such a policy would normally be used.
All three workflows were analyzed with no dangerous sinks or audit findings, but all eight action references are unpinned and two workflows grant top-level write permissions. These are workflow hygiene and least-privilege concerns, not severe risks on their own.
We didn't find any vulnerabilities for this package.
| 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.