Usable with caveats: the package is licensed, small, clearly documented, and backed by an organization, but it has had no release or commit activity for more than five years. It is not deprecated or archived, yet its maintenance appears effectively dormant.
55%
Total Score
63
100
83
80
The latest release was over five years ago, with no releases in the last 12 months and only three releases overall. This is the strongest concern because compatibility and maintenance may have stalled.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. That indicates a meaningful abandonment risk despite the repository remaining available.
There are no open issues or pull requests, which avoids an unresolved backlog but also shows no recent project activity. Given the long release gap, this does not compensate for dormancy.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a minor transparency gap rather than a standalone reason to reject this package.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. For a small, dormant extension this is a hygiene concern, but it is less important than the lack of maintenance activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/behat Version ^3.8 | — | — |
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.