chuxolab/laravel-fortress

Repo commit activitydanger

The repository has no commits and no active maintainers in the last 3 months. Combined with the roughly 6-month gap since the latest release, this is the strongest abandonment concern.

Maintainerscaution

Only one account has registry publishing access. The linked repository is user-owned rather than organization-owned, so there is no provided backing signal to compensate for this narrow publisher base.

Release historycaution

The package is about 6 months old but has only two releases, both published within minutes on its first day. That limited history provides little evidence of a sustained maintenance cadence.

Security policycaution

The repository has no security policy. For a package focused on security checks and application protection, that is a meaningful transparency gap.

Workflow auditcaution

Both workflows were analyzed without audit findings or untrusted-trigger sinks, but all seven action references are unpinned and the release workflow grants top-level write permissions. The broad token is only a mild concern here because no untrusted workflow path was observed.