Documentation, licensing, and release notes make the package easy to inspect. Maintenance has stopped since February, and all eight workflow actions are unpinned; the single-user project also has no security policy.
55%
Total Score
50
100
83
75
One registry publishing account is consistent with the repository being owned by the same individual, but it indicates limited maintainer capacity when combined with the lack of recent commits.
The package published six releases in its first 26 days, but the latest release was about seven months ago. The initial burst is positive, while the subsequent gap raises abandonment concern.
There were no commits and no active maintainers in the last three months, despite the repository not being archived. This is the clearest maintenance and abandonment concern.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is not by itself evidence that the package is unsafe.
Version v0.0.6 is not a stable-major release, so the API may still change. It is not marked as a prerelease, which partly offsets the early-version risk.
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.