It includes a clear README, tests, changelog, and MIT licensing, but has no security policy or automated security scanning. Its small dependency surface limits some maintenance exposure.
40%
Total Score
50
100
81
75
The latest release was published about 14 years ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk, although the repository is not archived.
There were zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates a project that is not receiving active maintenance.
The repository name does not match the package name, and its README does not mention this package. That weakens confidence that the linked repository is the package's dedicated source.
Composer is used as a build tool, but the repository has no security scanning tools. The missing scanning is a transparency and maintenance gap, though it is not evidence of malicious behavior.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package that handles cURL requests.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/symfony Version 2.* | — | — |
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.