20steps/oauth-server-bundle

Release historydanger

The package has 17 releases but none in the last 12 months; its latest release was about nine years ago. This strongly suggests the release line is abandoned, with no newer registry activity to compensate.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. This is a substantial abandonment concern.

Repo package mentioncaution

The repository name does not match the package name, and its README does not mention the package. Although organization-owned repositories can host sub-packages, this combination weakens confidence that the linked source is the package's maintained home.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are present. That is a modest supply-chain hygiene gap, especially for a security-sensitive integration package.

Security policycaution

The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. This is a transparency and maintenance gap for an OAuth server component.