yadavsourabhgh/mongo-keepalive

Maintainerscaution

Only one registry publishing account is listed. That can be adequate for a personal project, but it leaves limited visible publishing redundancy and increases bus-factor concerns.

Release historycaution

There has been only one release, published about 6 months ago, so there is not enough release history to demonstrate sustained maintenance or compatibility over time.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible community adoption provides no external evidence of maturity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap, though not evidence that the package is unsafe.

Security policycaution

No security policy is present. For a library that connects to MongoDB, the lack of documented vulnerability-reporting guidance is a genuine transparency gap.