mongdch/mon-auth-think

The MIT license, README, stable versioning, and regular releases provide a clear basis for adoption. The single maintainer, zero recent commits, and lack of security scanning leave maintenance capacity and oversight weaker than ideal.

Latest 1.2.6

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed. That is a limited publishing base and increases continuity risk, especially alongside the repository's single-user ownership context.

Project backing

The repository is owned by a user account rather than an organization, and the registry namespace also maps to that individual context. Combined with one registry maintainer, this suggests limited organizational backing.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the recent release history provides some compensating evidence.

Repo popularity

The repository has zero stars and forks and one watcher. This indicates little visible adoption or community support, but popularity alone does not establish that the package is unsafe to depend on.

Repo tooling

Composer is used as the build tool, but no security scanning tool was detected. The missing scanning coverage is a modest transparency and oversight gap.