muhammadsalman/laravel-sso

Release historydanger

Only two releases were published, both within about two days, followed by no release in roughly 13 months. That short history and long pause indicate elevated abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers during the last three months, consistent with roughly 13 months without a push. This is strong evidence of stalled maintenance.

Maintainerscaution

One registry publisher account is consistent with a small user-owned project, but it leaves little visible publishing redundancy when combined with the absence of recent activity.

Project backingcaution

The source repository is owned by an individual account rather than an organization, and no broader project backing is shown. That leaves a thin maintenance base alongside the inactive commit history.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no external adoption signal to offset the short history and inactivity.