The project has recent repository activity, tests, release notes, a matching repository, and a valid license. Maintenance depends on one active contributor, while all nine workflow actions are unpinned and the repository has no security policy.
64%
Total Score
70
100
88
50
Only one registry account has publish access, which creates a narrow publishing point. The repository's recent activity shows that this maintainer is active, but does not remove the single-person continuity risk.
The repository is owned by an individual account, so the single-contributor and single-publisher concentration is not offset by organization backing.
The package has 17 releases over about 15 months, but only one release in the last 12 months. Recent repository activity partly offsets the slow registry cadence, but the release pattern warrants caution.
All four recent commits came from one contributor, so maintenance and release continuity are concentrated in a single person.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpstan/phpstan Version ^2.1.36 | — | — |
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.