daandelange/tabsfield

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base for continuity, although the linked repository is also owned by the same individual, so the ownership is consistent rather than unexplained.

Project backingcaution

The registry namespace and repository are owned by the same individual account, rather than an organization. This is consistent ownership, but it also means there is no demonstrated organizational backing to offset the thin maintainer base.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. For a small mature plugin this may reflect stability, but it leaves current maintenance capacity unproven.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a hygiene limitation rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy file. That weakens vulnerability-reporting transparency, but it is not by itself evidence of abandonment.