Healthy and suitable to use, with a small maintainer-risk caveat. It has frequent recent releases, active development, tests, and clear licensing, but all recent commits come from one contributor and the repository lacks a security policy.
82%
Total Score
67
89
80
The repository is owned by an individual user rather than an organization, so the one-person commit concentration represents a genuine succession risk rather than an organization-managed maintainer structure.
All 13 commits in the last three months came from one contributor, leaving maintenance highly dependent on a single person and creating a meaningful continuity risk.
The repository has zero stars and forks and only one watcher, providing little independent evidence of community adoption. This is supporting evidence only and is outweighed by the active release and commit history.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a transparency gap, though it does not outweigh the package's active maintenance and tests.
No repository security policy was found, so the project gives no documented channel or process for reporting vulnerabilities. This lowers transparency but is not by itself evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^7.4 | — | — |
symfony/config Version ^7.4 | — | — |
monolog/monolog Version ^3.9 | — | — |
symfony/console Version ^7.4 | — | — |
google/apiclient Version ^2.18 | — | — |
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.