tonegabes/filament-better-options

Maintainerscaution

Only one registry account has publishing access. That is a modest resilience concern for a user-owned project, although the active release history provides some compensation.

Project backingcaution

The registry namespace and repository belong to the same individual user account. This confirms ownership alignment but does not provide organizational backing or a broader maintainer base.

Repo commit activitycaution

The repository had zero commits and zero active maintainers in the last three months. Although releases were frequent over the past year, the current lack of source activity raises maintenance risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a hygiene gap rather than evidence that the package is unsafe.

Workflow auditcaution

All three workflows were analyzed with no untrusted checkouts, script injections, or audit findings. However, all 8 action references are unpinned and one workflow grants top-level write permissions, creating avoidable workflow-maintenance and token-scope risk.