ursuleacv/oauth2-lightspeed

Maintainerscaution

Only one registry account has publishing access. Because the project is user-owned rather than organization-backed, the narrow publishing base adds some continuity risk.

Project backingcaution

The registry namespace and repository are owned by the same individual, confirming consistent ownership but not organizational backing. This provides identity continuity without adding redundancy to the maintainer base.

Release historycaution

The package has 33 releases over about 10 years, but it has had no release in about 22 months. The long history helps maturity, while the recent pause raises maintenance concerns.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. This is direct evidence of currently stalled maintenance for a dependency that may need compatibility fixes.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanner is a hygiene gap, not evidence of a security incident.