kirschbaum/drupal-behat-remote-api-driver

Release historydanger

Only two releases were published, both in March 2015, with no releases in the last 11 years. That is strong evidence of abandonment for a package intended to support an evolving testing stack.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with its last push being about 11 years ago. This leaves defects and compatibility changes unlikely to receive attention.

Dependency profilecaution

The package declares 14 runtime dependencies and its README requires Behat 2 and DrupalExtention 1, an old and tightly coupled integration stack. That creates substantial compatibility and maintenance risk for new consumers.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security-scanning tools are configured. That is a transparency and maintenance gap, especially for an old dependency-heavy package.

Security policycaution

The linked repository has no security policy. This weakens vulnerability-reporting transparency, although it is secondary to the much stronger abandonment evidence.