marcoconsiglio/faker-php-number-helpers

Maintainerscaution

Only one account has registry publish access. That is a meaningful continuity risk for a user-owned project, even though the repository is clearly tied to the same owner.

Project backingcaution

The registry namespace and repository owner both identify the same individual user account. This confirms ownership alignment, but it does not provide organizational backing to compensate for the single-maintainer model.

Repo commit activitycaution

The repository had zero commits and zero active maintainers in the past three months. With no compensating recent development activity, this is the clearest maintenance concern.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers confidence in community support but does not make the package unhealthy by itself.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a hygiene gap rather than a severe adoption blocker.