karster/mozify

Maintainerscaution

Only one registry publishing account is listed. That is not inherently unhealthy for a small user-owned project, but it provides limited publishing redundancy alongside the inactive repository.

Project backingcaution

The registry namespace and repository belong to the same individual account, and the repository is user-owned rather than organization-backed. This is consistent ownership evidence but offers limited institutional continuity.

Release historycaution

Only two releases exist, with none in the last 12 months and the latest published over four years ago. This materially raises maintenance and abandonment risk.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release and indicating likely abandonment risk.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.