Set of Behat extensions
68%
Total Score
caution
No commits in the last three months and all workflow actions are unpinned, despite a current release and clean workflow audit.
The registry namespace and repository are owned by the same individual account. This is coherent ownership, but it provides less organizational continuity than an organization-backed project.
The package has four releases over about 830 days, with two releases in the last 12 months, but the median interval is about 261 days. This indicates an infrequent but recently active release pattern.
The repository recorded zero commits and zero active maintainers during the last three months. Although the current release was recently published, the short-term commit silence weakens maintenance confidence.
The repository has one star, one fork, and one watcher. This is limited supporting evidence and leaves little external adoption signal, though popularity alone does not determine package health.
The repository has no published security policy. This is a transparency gap for reporting vulnerabilities, although security scanning is present.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
behat/behat Version ^3.17 || ^4.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.