khooz/oath

Usable with caveats: the package is clearly identified, MIT-licensed, dependency-light, and not deprecated or archived. However, its last release and repository activity were over six years ago, with very little adoption and no security policy or scanning, so verify it still meets your needs before adopting it.

Latest 6.0

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers during the last three months, consistent with more than six years without observed repository updates and raising abandonment risk.

Release history

Only four releases exist since January 2015, and the latest release was on March 10, 2020, with no releases in the last 12 months. This is a meaningful maintenance concern for a security-related authentication library.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. While this may indicate a quiet project, it also shows no recent community or maintainer engagement.

Repo popularity

The repository has only 3 stars, 2 forks, and 1 watcher. Low popularity is supporting evidence rather than decisive by itself, but it provides little evidence of broad review or community support.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. For an OTP library, the lack of automated security checks is a meaningful hygiene gap.