afosto/oauth-client

Release historydanger

There has been only one release, published about 9 years ago, with no releases in the last 12 months. That is strong evidence of an effectively inactive package, despite the absence of registry deprecation.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last 3 months. Combined with the old last push, this materially raises abandonment risk.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tooling is present. The missing scanning is a modest hygiene gap, not as significant as the prolonged inactivity.

Security policycaution

The repository has no security policy. For a small, inactive OAuth provider, this reduces transparency around vulnerability reporting and leaves a genuine maintenance gap.

Version stabilitycaution

The assessed version is the sole 0.0.1 release and is not a stable major version. This adds maturity risk, although it is not marked as a prerelease.