bitmotion/single-signon

Registry deprecationdanger

Packagist marks the entire package as abandoned and provides leuchtfeuer/auth0 as a replacement, which is a severe adoption risk for this release.

Release historydanger

Only two releases were recorded, with the latest on May 9, 2018 and none in the last 12 months; this indicates long-term abandonment rather than an actively maintained package.

Repo commit activitydanger

The linked repository has recorded zero commits and zero active maintainers in the last three months, with its last push in January 2022, so current maintenance capacity is not evident.

Repo package mentioncaution

The linked repository name does not match bitmotion/single-signon, and no README package mention was available, creating uncertainty about the repository-to-package relationship; organization backing partly offsets that concern.

Security policycaution

The linked repository has no security policy, which leaves vulnerability reporting and response expectations undocumented; the absence of recent maintenance makes this gap more consequential.