Tests, documentation, and release notes provide useful maintenance context, and the repository is not archived. The missing security policy and security scanning reduce transparency.
58%
Total Score
25
71
83
The latest release was nearly four years ago, with no releases in the last 12 months. This strongly raises abandonment risk despite 13 releases during the package's earlier history.
The repository recorded zero commits and zero active maintainers in the last three months, confirming that development has stopped rather than merely slowed.
There were no new or closed issues or pull requests in the last month, while two issues remain open. This provides no evidence of ongoing support.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance weakness, not evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for an API client that may handle authentication tokens.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
abraham/twitteroauth Version ^4.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.