zhamao/request

Tests, release notes, and an Apache-2.0 license improve transparency. The small repository audience and missing security policy leave less evidence for long-term support.

Latest 1.2.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only four releases since 2020, with no release in the last 12 months and the latest release about 19 months ago. This is meaningful evidence that maintenance may have slowed.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the stale release cadence, this raises abandonment risk.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so ownership of the published package is not clearly established. Organization backing helps but does not remove this ambiguity.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is not decisive, but this provides little supporting evidence of broad use or community resilience.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance-process gap.