adamwathan/eloquent-oauth

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement provided. This is a severe adoption risk even though the specific release is not separately withdrawn.

Release historydanger

The latest registry release was in October 2015, nearly 11 years ago, and there were no releases in the last 12 months. The package has a long release history, but it has effectively stopped shipping.

Repo commit activitydanger

The repository had no commits and no active maintainers in the last three months, consistent with the long release gap. This indicates a substantial abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That weakens automated security coverage without indicating a direct defect in the release.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it is secondary to the package's broader maintenance concerns.