iliaal/pdo_duckdb

This release appears healthy and reasonable to depend on: it is not deprecated or archived, has a clear BSD-3-Clause license, a substantial README and changelog, repository-backed tests, reproducible-looking release workflows, security policy, read-only workflow permissions, and very recent activity with 92 commits and four merged pull requests in the last month. The main risks are that the package is young (77 days old), remains below a stable major version, and all recent commits come from one contributor, creating a meaningful bus-factor concern. Overall, the active maintenance and strong repository hygiene outweigh those risks, but teams should monitor continuity and expect possible API changes before 1.0.

Latest 0.7.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a limited publishing base, though the linked repository shows that the same named maintainer is actively developing the project.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational maintenance redundancy to offset the concentrated contributor base.

Repo bus factor

One contributor made all 92 commits in the last three months, producing a complete concentration of recent development. With a user-owned rather than organization-owned repository, this is a genuine continuity and bus-factor concern.

Repo popularity

The repository has 17 stars and no forks or watchers. This is limited ecosystem adoption evidence, but popularity is supporting evidence and does not outweigh the stronger maintenance signals.

Version stability

Version 0.7.1 is not a stable major release, so compatibility changes remain possible. It is not marked prerelease and recent releases have no prerelease share, which partly offsets the maturity concern.