The MIT license, README, release notes, and small dependency set make adoption straightforward. Keep an eye on maintenance ownership and CI changes; the repository is active but recent work is concentrated.
70%
Total Score
83
100
94
75
All three recent commits came from one contributor, creating a thin active maintainer base. Organization ownership provides some handoff capacity, but no second active contributor is evidenced.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for users and maintainers.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all six action references are unpinned, which weakens CI reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/behat Version ^3.5 || ^4.0 | — | — |
friends-of-behat/mink-extension Version ^2.3 || ^3.0 | — | — |
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.