phper666/hyperf-server-command

Release historydanger

The last release was over six years ago, with no releases in the past 12 months. That long period without updates is a substantial abandonment risk despite a regular early release cadence.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having stopped changing since 2020. This leaves little evidence of current maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a hygiene limitation, not as serious as the absence of current development activity.

Repository archivedcaution

The repository is not marked archived, but its last push was over six years ago. The active archive flag is reassuring, while the old repository state still supports the maintenance concern captured by the activity signals.

Security policycaution

No security policy was found in the repository, so there is no documented process for reporting or handling vulnerabilities. This reduces transparency for a package with no recent maintenance evidence.