A clear README, tests, and MIT licensing improve day-to-day adoption. Its small, single-owner project has had no release or commit activity since August 2023, so maintenance risk remains.
58%
Total Score
50
100
88
50
Only one registry publishing account is listed. This is a thin maintainer base for a user-owned project and increases continuity risk when combined with the absence of recent activity.
The package has had no releases in the last 12 months, and its latest release was in August 2023. This materially raises abandonment risk despite four releases overall.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the project having stopped changing after August 2023.
Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and maintenance-hygiene gap, not a severe risk on its own.
The repository has no security policy. For a small package this is a minor disclosure and maintenance gap, while the available README and source tree provide some compensating transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version >=1.0 | — | — |
guzzlehttp/guzzle Version >=6.4 | — | — |
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.