smartfactory/oauth2

The MIT license, API documentation, and small dependency surface make integration straightforward. A single publisher and no automated security tooling reduce confidence in long-term support.

Latest 1.2.25

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. The repository is user-owned rather than organization-backed, so this leaves a meaningful bus-factor concern despite the recent release.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. This is partly offset by the November 2025 release, but it leaves current maintenance activity unclear.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little external evidence of broad adoption or review.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security-scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.

Security policy

The repository has no security policy. For an OAuth2 server, the absence of a documented vulnerability-reporting process is a genuine support and transparency concern.