ribal/onix

Maintainerscaution

Only one registry account has publishing access, leaving a thin publishing base. This is a meaningful continuity concern because the project is user-owned rather than organization-backed.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the past three months. The recent push and registry releases provide some counter-evidence, but the lack of sustained source activity makes maintenance less certain.

Repo toolingcaution

Composer is used for builds, but no security scanning tools were detected. That is a hygiene gap for a dependency library, though it is not by itself evidence that the release is unsafe.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency and response expectations, but the absence is a moderate governance gap rather than a release blocker.