allure-framework/allure-behat
The package is clearly licensed, documented, and backed by an organization with a matching repository. Its registry release history is stale, with no releases in the last 12 months, and repository activity shows no active maintainers or commits in the last three months.
58%
Total Score
67
100
88
100
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest registry release was in September 2018. That long release gap materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release history, this is a meaningful maintenance concern.
There were no new or closed issues or merged pull requests in the last month, while 10 pull requests remain open. This suggests limited recent project throughput.
All three workflows were analyzed successfully and use read-only permissions, with no high- or medium-severity findings or untrusted checkout and script-injection patterns. All four action references are unpinned, a minor reproducibility and workflow-hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Eduard Sukharev |
| Tiko Lakin |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 behat/behat Version ^3.3 | — | — |
allure-framework/allure-php-api Version ~1.1.4 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.