The focused package has a clear README and a source repository that matches its name. However, maintenance appears abandoned: the last release and repository push were more than eight years ago, with no recent commits or active maintainers. Composer-based packaging and an MIT declaration are otherwise straightforward.
42%
Total Score
0
71
75
The latest release was published on July 30, 2018, and there have been no releases in the last 12 months despite the package being more than eight years old. This is strong evidence of abandonment for an API client whose upstream service may change.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided maintenance signal compensates for this lack of recent source activity.
The repository uses Composer, but no security scanning tools were detected. This is a supporting hygiene gap rather than the main concern, because the much longer maintenance lapse carries more weight.
The linked repository is not archived, which leaves the project technically open to maintenance. However, its last push was on July 30, 2018, so the non-archived status does not offset the observed inactivity.
No security policy was found in the repository. That reduces transparency for reporting and handling vulnerabilities, although it is secondary to the absence of recent releases and commits.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0 | — | — |
monolog/monolog Version ^1.23 | — | — |
guzzlehttp/guzzle Version ~6.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.