fightbulc/easy_pdo

The README, declared BSD-2-Clause license, and absence of install-time scripts make the package straightforward to inspect and use. Its tiny repository has little community interest and no security policy or scanning, increasing the cost of future maintenance.

Latest 0.1.8

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, with the latest on March 4, 2013 and none in more than 13 years. This is strong evidence of abandonment for a database library that may need compatibility and security maintenance.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing signal to offset the very old activity.

Repo issue activity

There are no open issues or pull requests and no recent activity, which may indicate stability but, alongside the old release history, also shows no visible maintenance engagement.

Repo popularity

The repository has only 3 stars and 1 fork, providing little evidence of broad review or community support. Popularity is supporting evidence, but this reinforces the maintenance concern.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. That leaves an avoidable transparency and maintenance gap for a database-access library.