The repository was updated recently and includes extensive tests, a README, and release notes. Maintenance is concentrated in one contributor, and the project has no security policy or scanning tools, but organizational ownership and a current stable release reduce the concern.
82%
Total Score
83
100
88
83
The package has only three releases over roughly 3.6 years, with one release in the last year and a median interval of about 20 months. That is a slow cadence, though the latest release is recent.
All four recent commits came from one contributor, creating a real continuity risk. Organization ownership partly compensates because maintenance can potentially be handed off.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a process gap, not evidence of an unsafe release.
No repository security policy was found, leaving vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^2.0|^3.0 | — | — |
webmozart/assert Version ^1.11 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
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.