davedevelopment/behat-registry

Release historydanger

There has been only one release, published over 13 years ago, with no releases in the last 12 months. This is strong evidence of stagnation for a package that may need compatibility or security fixes.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the very old latest release, this indicates little current maintenance capacity.

Repo issue activitycaution

There are no open issues or pull requests, and no recent issue or pull request activity. This is neutral for a tiny stable package, but it provides no evidence of active support.

Repo popularitycaution

The repository has 1 star, 2 forks, and 1 watcher, showing a very small user and contributor base. Popularity is supporting evidence rather than decisive, but this offers little external maintenance capacity.

Repo toolingcaution

Composer is used for the build, but no security scanning tooling is present. For this small, inactive project that is a modest transparency and maintenance gap.