conquer/oauth2

The package is clearly documented, licensed, tested, and has a small dependency set. Its single-maintainer project has no security policy or automated security scanning, which increases the cost of relying on an aging OAuth implementation.

Latest 1.7.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published over seven years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment for a security-sensitive library, despite its earlier 13-release history.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release gap and leaving little evidence of ongoing maintenance.

Maintainers

Only one registry account has publish access. That can be normal for a user-owned project, but it leaves a thin publishing and maintenance base when combined with the long period of inactivity.

Repo issue activity

There are six open issues and no issues or pull requests were opened or closed in the last month. This supports the broader picture of limited current project activity, but is not independently severe.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. For an OAuth server library, that is a meaningful hygiene gap, though it is less severe than the long maintenance pause.