sirix/mezzio-routing-contracts

Maintainerscaution

Only one registry account has publishing access. That is a modest continuity concern for a user-owned project, although recent release activity provides some compensation.

Project backingcaution

The registry namespace and repository are associated with the same individual user rather than an organization. This provides direct ownership consistency but limited organizational continuity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a transparency gap, though other workflow controls are healthy.

Security policycaution

The repository has no security policy. For a small contracts package this is a genuine disclosure-process gap, but it is not evidence that the package is unmaintained.