Package Health/frontkom/common-behat-definitions

frontkom/common-behat-definitions

The package is clearly licensed and has a focused README with a matching source repository. Maintenance has gone quiet for about 14 months, with only two releases overall, no recent commits, and no security policy or scanning.

Latest 1.0.1

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, following the last push about 14 months ago. This materially raises abandonment risk.

Release history

There have been only two releases, and none in the last 12 months; the latest release was about 14 months ago. This is a meaningful maintenance concern for a dependency, although the package may be intentionally stable.

Repo issue activity

There are no new or closed issues in the last month and one open pull request, providing little evidence of active project handling.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher. Low visibility is supporting caution rather than a verdict, especially for a small development helper.

Repo tooling

Composer is used for builds, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.