mixu/sso-auth

The package is clearly documented and includes a license, changelog, and substantial source tree. Its single-person ownership, absent security scanning and policy, and zero commits in the last three months leave maintenance and response capacity uncertain.

Latest v1.1.8

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is limited visible publishing continuity if that maintainer becomes unavailable.

Project backing

The repository owner is an individual user rather than an organization, which provides less visible institutional backing for a security-sensitive dependency.

Release history

There have been 13 releases in about seven months, but the median interval is about 3 hours 46 minutes, suggesting a concentrated burst rather than established long-term cadence.

Repo commit activity

The repository has zero commits and zero active maintainers in the last three months. For a package with a recent release, this is a meaningful warning about ongoing maintenance capacity.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for community review, but the package is still relatively young, so it is not decisive.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Mixu

Direct Dependencies

Dependency	Last Release	Score
illuminate/auth Version ^11.0 \|\| ^12.0 \|\| ^13.0	—	—
illuminate/http Version ^11.0 \|\| ^12.0 \|\| ^13.0	—	—
illuminate/support Version ^11.0 \|\| ^12.0 \|\| ^13.0	—	—
illuminate/database Version ^11.0 \|\| ^12.0 \|\| ^13.0	—	—
illuminate/contracts Version ^11.0 \|\| ^12.0 \|\| ^13.0	—	—