stevenmaguire/oauth2-basecamp

Release historycaution

Only two releases have been published, with no release in about four years and a median interval of about 878 days. The documented 0.2.0 release provides some maturity, but the long inactivity raises abandonment risk.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Repo toolingcaution

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

Repository archivedcaution

The linked repository is not archived, although its last push was about four years ago. The active repository status partly offsets, but does not remove, the maintenance concern.

Security policycaution

The repository has no security policy. For an OAuth client provider, the absence reduces transparency for reporting and handling security issues.