moyer/qtemp

The README is detailed, and the two runtime dependencies keep integration relatively straightforward. A single publisher and no visible community activity limit confidence in long-term support.

Latest v1.9.1

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publisher is listed. Recent release activity partly compensates, but a single publishing account leaves limited visible continuity if that maintainer stops contributing.

Project backing

The repository is owned by an individual user rather than an organization, offering less visible institutional backing. Recent releases provide some compensation, but not a broader support signal.

Repo issue activity

The repository has no open issues or pull requests and recorded no issue or pull-request activity in the last month. This may reflect a small, quiet project rather than abandonment, so the effect is limited.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is not required for health, but these counters provide no supporting evidence of community adoption or review.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This is a transparency and maintenance gap, though it does not by itself make the release unfit.