The stable version, release notes, tests in the repository, and clear licensing make the package straightforward to evaluate. Its last release was over 12 years ago, with no recent commits and limited compatibility, so future support is uncertain.
40%
Total Score
50
79
50
The package has had only three releases, all within about six days in July 2014, and none in the last 12 months. This long release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no observable current maintenance.
There is one open issue but no new or closed issues and no pull-request activity in the last month. This is limited evidence of current project engagement and reinforces the maintenance concern.
The repository uses Composer, but no security scanning tools were detected. That is a modest transparency and hygiene gap, not a severe dependency risk by itself.
No security policy was found in the repository. For a small testing extension this is a minor transparency gap, but it provides no documented route for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/behat Version ~2.4 | — | — |
guzzle/guzzle Version 3.* | — | — |
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.