lhsazevedo/sh4objtest

Maintainerscaution

Only one registry account has publishing access. The repository is also owned by the same individual, so there is no organizational backing shown to offset this concentration.

Project backingcaution

The registry namespace and repository owner are the same individual user, confirming package ownership alignment but providing no broader organizational backing.

Repo bus factorcaution

All 67 recent commits came from one contributor, creating a meaningful continuity risk if that person becomes unavailable.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.