phlib/db-helper

Clear documentation, repository tests, and release notes support adoption. Organization backing and an unarchived repository help, but quiet activity, no security scanning, and weak CI pinning reduce confidence.

Latest 3.0.1

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since April 2017, but it has only six releases and none in the last 12 months; the latest release was in February 2025. This indicates a mature but currently quiet maintenance pattern.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with a project that has gone quiet since its latest release. For a library dependency, this raises abandonment and issue-response concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence that the package is unsafe.

Security policy

The repository has no published security policy, leaving vulnerability reporting and response expectations undocumented.

Workflow audit

The only workflow was fully analyzed, but all four action references are unpinned and the audit found a high-confidence container image using the floating latest tag. The workflow has no untrusted checkout or script-injection findings, which limits the concern.