hyperf/memory

Usable with caveats: it has a long release history, recent releases, active organizational backing, and no deprecation or archive status. The main concerns are the missing README and very limited recent development activity, with permissive workflow configuration adding some maintenance risk.

Latest v3.2.5

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Dangerous workflows

One of two workflows uses pull_request_target, which can increase workflow risk when handling untrusted pull requests. No untrusted checkout or script-injection patterns were detected, limiting the concern.

Package scaffolding

The published artifact has no README, which makes integration less transparent for a library consumers must understand. Missing tests and changelog files in the artifact are normal packaging practice, while the repository's GitHub release workflow provides some release structure.

Repo bus factor

All one recent commit came from a single contributor, creating concentrated recent maintenance capacity. Because the repository is organization-owned, handoff capacity is better than for a personal project, but no second active contributor is shown.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. Recent releases and the non-archived organizational repository compensate partly, but the current maintenance pace is thin.

Repo issue activity

There is one open issue and no issue or pull-request activity in the last month. This is limited evidence of community engagement, but not enough alone to indicate abandonment.