iam-deep/form-tool

Maintainerscaution

Only one registry account has publishing access. This is a modest resilience concern, although the repository's active release and commit history shows that publishing and development are currently happening.

Project backingcaution

The registry namespace and repository are owned by the same individual account. This provides direct ownership alignment but does not provide organizational succession or support.

Repo bus factorcaution

All 36 recent commits came from one contributor, creating a clear single-maintainer continuity risk with no second active contributor shown.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 1 watcher, so external adoption and review appear limited; this is supporting caution rather than evidence that the package is unfit.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. The missing scanning is a transparency gap, though it is not by itself evidence of unsafe maintenance.