phpgo/hyperf-logging

Project backingcaution

The package uses the phpgo registry namespace but the linked repository is owned by an individual account rather than an organization. This does not prove weak backing, but it provides limited organizational maintenance assurance.

Release historycaution

This is the first release and the package is 0 days old, with only one registry release. That is expected for a new package but provides no evidence of sustained maintenance.

Repo commit activitycaution

The repository has zero commits and zero active maintainers in the past 3 months. Because the project is newly published, this is not evidence of a collapse, but it leaves ongoing maintenance unproven.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap, partly offset by the repository's documented tests and strict validation in the release notes.

Security policycaution

The repository has no security policy. For a new logging integration this is a transparency gap, although the available evidence does not show a security incident or unsafe behavior.