lbaey/chromedriver

Release historydanger

The latest release was published nearly nine years ago, with no releases in the last 12 months. That is a substantial abandonment risk for a tool whose downloaded drivers must track changing platforms.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, and its last push was over five years ago. This strongly limits confidence that compatibility problems will be addressed.

Maintainerscaution

Only one registry publishing maintainer is listed, so there is little visible publishing redundancy for a user-owned project. The linked repository confirms the package identity but does not offset the narrow maintainer base.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This supports the evidence of inactive maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and maintenance gap rather than evidence of unsafe behavior by itself.