Package Health/aberdeener/minecraft-oauth

aberdeener/minecraft-oauth

Usable with caveats: the package is licensed, documented, tested, and not deprecated, but it has had no release or repository activity for about 3 years 5 months. Its very small project footprint and lack of security policy also make long-term maintenance uncertain.

Latest 0.1.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, with none in the last 12 months; the latest release was about 3 years 5 months ago. That long release gap is a meaningful maintenance concern for an OAuth integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the long period since the last push and indicating likely abandonment risk.

Repo issue activity

There are no open issues or pull requests and no recent issue activity. This is not itself harmful, but it provides no evidence of an active support process.

Repo package mention

The repository name matches the package, which supports the link, but the README does not mention the package name. This creates a small ownership and package-to-repository transparency concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. For a package handling OAuth credentials and tokens, that is a modest transparency and maintenance gap.