grosv/laravel-passwordless-login

Project backingcaution

The repository is user-owned rather than organization-owned, so the concentrated recent contribution pattern carries more continuity risk than it would with clear organizational backing.

Repo bus factorcaution

Two contributors were active, but one made 95% of the 20 recent commits. This creates a genuine continuity risk despite the second contributor remaining active.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting guidance unclear. This is a transparency gap, but not evidence of abandonment.

Token permissionscaution

Six workflows lack top-level token permissions and one declares top-level write access; although some jobs use job-level permissions, the repository could restrict automation privileges more consistently.