sergeytsalkov/meekrodb

Healthy and reasonable to depend on, with a long release history, a current stable release, and a matching maintained repository. The main caveats are that recent work is concentrated in one contributor and the repository has no security policy or automated security scanning.

Latest v3.1.5

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository and registry namespace are owned by the same individual, providing a consistent ownership link, but no organization-level backing is present to offset the single-maintainer risk.

Repo bus factor

All one recent commit came from a single contributor, leaving maintenance dependent on one individual and increasing abandonment or handoff risk.

Repo commit activity

There was one commit in the last three months from one active maintainer. This shows recent activity but indicates a very low maintenance tempo.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured. The missing scanning automation is a transparency and maintenance gap, though it is not evidence that the package is unsafe.

Security policy

The repository has no SECURITY.md or other detected security policy, so users lack documented guidance for reporting vulnerabilities and handling security issues.