beechit/bynder

The linked project is not archived and matches the package, with a usable README, release record, and small dependency set. Security scanning and a security policy are absent, while five pull requests remain open without recent activity.

Latest 0.0.3

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases, with the latest published in October 2018 and none in the last 12 months. This long release gap is a strong abandonment concern for a production integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale registry release history, this indicates a substantial maintenance and abandonment risk.

Lifecycle scripts

A post-autoload-dump install-time script is present. Composer lifecycle hooks can execute package code during installation, so this deserves review even though the indicator provides no evidence that the script is harmful.

Repo issue activity

There are five open pull requests but no new or merged pull requests in the last month, suggesting that proposed work is not currently being integrated.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That is a transparency and maintenance weakness for a package that handles external service credentials.