The repository has no security policy or scanning, and adoption appears minimal. The MIT license, readable README, and non-deprecated status help, but no release in over nine years makes maintenance risk substantial.
40%
Total Score
50
81
50
The latest release was published over nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, though the package is not marked deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This weakens confidence that defects or compatibility issues will be addressed.
The repository has 0 stars, 1 fork, and 1 watcher, providing little supporting evidence of broad community use or review. Low popularity is not decisive for a small testing helper, but it adds to the maintenance uncertainty.
Composer build tooling is present, but no security scanning tools were detected. That limits automated oversight, although the absence of scanning alone does not show a security defect.
The repository has no security policy. This reduces transparency about vulnerability reporting and response, with no provided compensating security process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/mink Version ^1.7 | — | — |
behat/mink-zombie-driver Version dev-master@dev | — | — |
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.