stevenmaguire/oauth2-elance

Release historydanger

The package has only two releases, with the latest on January 26, 2017 and none in the last 12 months. That long release gap is a substantial abandonment concern, although the stable 2.0.0 release is documented.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push in 2017. This indicates the project is not receiving ongoing maintenance.

Project backingcaution

The registry namespace and repository are owned by the same individual, and the repository name matches the package. This provides direct ownership alignment, but no organization backing is shown to compensate for inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe dependency risk.

Repository archivedcaution

The linked repository is not archived, which leaves the project technically available for maintenance. However, its last push was in 2017, so the unarchived status does not offset the observed inactivity.