latchvector/sso

This is a promising but very young package: it has a stable 1.1.2 release, seven releases over 38 days, recent repository activity, substantial documentation, tests, a changelog, and a clear MIT license. The main adoption risks are that all recent commits come from one contributor, the repository has no security scanning or security policy, and the project has no established popularity yet. It is not deprecated or archived, and its packaging and release cadence provide meaningful evidence of active development, so it appears usable but should be adopted with normal dependency monitoring and attention to maintainer continuity.

Latest 1.1.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The linked repository is owned by a user rather than an organization, so there is no provided project-backing evidence that compensates for this concentration.

Project backing

The repository owner is a user account rather than an organization, so the assessment has no organization-level backing evidence to offset the single-maintainer concentration.

Release history

The package is only 38 days old, which limits evidence of long-term maintenance, but seven releases with a median interval of about 5 days show active iteration rather than abandonment.

Repo bus factor

One contributor made all 12 commits in the last three months, creating a significant continuity and abandonment risk for a user-owned project.

Repo popularity

The repository has zero stars, forks, and watchers. This is not a health verdict by itself, but it provides no external adoption or review signal for this young package.