phlib/db

Clear documentation, licensing, and an organization-backed repository make this release straightforward to inspect. Inactive recent development and the workflow’s floating container image warrant caution for long-lived production use.

Latest 3.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since April 2016 and has 12 releases, but it has made no release in the last 12 months; the latest release was in February 2025. The long gap lowers confidence in ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the long release gap, this is meaningful evidence of currently inactive development.

Repo issue activity

There are only two open issues, no open pull requests, and no issue or pull-request activity in the last month. This is limited evidence of current project engagement, but not by itself severe.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a modest transparency gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy. For a database adapter, this leaves vulnerability-reporting expectations unclear and modestly reduces maintenance transparency.