Risky to adopt: the package has had no release since July 2016 and no recent repository activity, making abandonment the main concern. It is licensed, documented, tested, and not deprecated or archived, but those positives do not offset its age.
40%
Total Score
25
75
75
The latest release was published in July 2016, with no releases in the last 12 months. Nearly 10 years without a release is strong evidence of an unmaintained dependency, despite the package having seven historical releases.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long gap since the last release. This leaves little evidence that defects or compatibility issues will be addressed.
Only one registry account has publishing access. That is a limited maintainer base for an independently owned project and increases continuity risk, although the linked repository identifies the same owner.
The repository is not marked archived, which is a positive signal, but its last push was in July 2016 and does not compensate for the absence of current activity.
The repository has no security policy. This is a transparency gap, though it is secondary to the much stronger evidence of long-term inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/behat Version ~3.1 | — | — |
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.