codeception/remote-debug

Release historydanger

The latest release was in June 2016, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the release history and indicating effectively inactive maintenance.

Repo issue activitycaution

One issue and one pull request remain open, with no new or closed activity in the last month. This provides no evidence that maintenance requests are being handled.

Repo popularitycaution

The repository has only 9 stars and 2 forks, so there is little visible community support to compensate for the inactive maintainer.

Repo toolingcaution

Composer is used for the build, but no security scanning tool is configured. That is a minor transparency gap, while the absence of scanning does not by itself indicate abandonment.