beshkin/micloud-php

Release historydanger

This is the only release, published about four years ago, with no releases in the last 12 months. That strongly limits evidence of active maintenance.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base for a user-owned project and increases continuity risk if the maintainer stops work.

Project backingcaution

The registry namespace and repository are owned by the same individual account, confirming ownership alignment but offering no organizational backing to compensate for the thin maintainer base.

Repo popularitycaution

The repository has zero stars and forks and one watcher, providing little supporting evidence of community adoption or review.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. This is a hygiene gap that adds some transparency and maintenance concern.