Risky to adopt: the package has had no release or repository activity for about nine years, leaving maintenance and compatibility concerns. It is still licensed, backed by an organization, and includes repository tests, but those strengths do not offset the prolonged stagnation.
42%
Total Score
50
71
83
The latest release was published about nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment or unaddressed compatibility risk despite the package having nine historical releases.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the package's long release gap. The repository is not archived, but there is no observed current maintenance.
Composer is used for the build, but no security scanning tooling is present. The missing scanning is a transparency gap, though the larger concern remains the prolonged lack of maintenance.
The linked repository is not archived, which preserves a path for future maintenance. However, its last push was about nine years ago, so the non-archived status only partly compensates for the inactivity.
The repository has no security policy. For a worker-process component, this leaves vulnerability reporting and response expectations unclear, with no provided evidence of a compensating process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version 1.* | — | — |
sarehub/commons Version 0.5.* | — | — |
symfony/console Version 3.* | — | — |
symfony/process Version 3.* | — | — |
respect/validation Version 1.* | — | — |
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.