Clear documentation, release notes, and a long record of frequent releases support dependable maintenance. Most recent work comes from one contributor, and workflow actions are not pinned, leaving avoidable continuity and build-integrity concerns.
84%
Total Score
70
100
89
83
Only one registry account has publish access, which creates publishing continuity risk. The linked repository is actively maintained, but that does not remove the single-publisher concentration.
The registry namespace and repository are owned by the same individual, confirming ownership alignment. Individual ownership also means the concentrated maintainer base is a meaningful continuity risk.
One contributor made 95% of the last three months' commits, so maintenance depends heavily on a single person despite two additional active contributors.
The project uses Make and Composer build tooling, but no security-scanning tools were detected. This is a modest transparency and assurance gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpunit/phpunit Version <12.0.0 | — | — |
symfony/process Version >=4.4.24 <8.0 | — | — |
vlucas/phpdotenv Version ^5.0 | — | — |
symfony/filesystem Version >=4.4.24 <8.0 | — | — |
codeception/module-db Version ^2.0 || ^3.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.