inclitoleo/dbmysql

Usable with caveats: it has a current stable release, clear documentation, extensive tests, and active repository maintenance signals. The main concerns are a single maintainer, no commits in the last three months, and limited repository security controls.

Latest v3.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access, creating a meaningful continuity and bus-factor concern. The linked repository is user-owned rather than organization-backed, so there is no provided organizational support signal to offset it.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, despite a recent release and merged pull requests. This creates a maintenance-continuity concern because current development activity is not consistently visible.

Repo popularity

The repository has zero stars and forks and only one watcher, so there is little community adoption evidence. Popularity is supporting evidence rather than a decisive health measure, and the repository shows other maturity signals.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, though it is not by itself evidence that the package is unsafe or abandoned.

Security policy

The repository has no security policy, leaving vulnerability reporting and disclosure expectations undocumented. This is a transparency gap for a database connectivity library.