The project has clear documentation, a changelog, a license, and repository tests. Missing security tooling and a security policy, alongside one-person maintenance, leave useful but meaningful adoption caveats.
72%
Total Score
50
94
50
All 3 recent commits came from one contributor, giving that contributor a 100% share. The matching repository and recent releases help, but there is no observed second active contributor to provide continuity.
The repository had 3 commits in the last 3 months, showing recent activity, but that is a modest maintenance pace for a package with ongoing releases.
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and maintenance gap, though not evidence that the package is unsafe.
The repository has no published security policy. That makes vulnerability reporting and response expectations less clear for adopters.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^3.2.0 | — | — |
phpunit/phpunit Version ^13.0.0 | — | — |
lastdragon-ru/path Version self.version | — | — |
sebastian/comparator Version ^8.0.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.