hashandsalt/kirby4-seo

Release historydanger

Only two releases exist, both from the initial release period, with none in the last 12 months; the package has had no registry release for nearly three years. This is the main abandonment concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the past three months. For a package already showing no recent registry releases, this strengthens the concern that maintenance has stalled.

Project backingcaution

The repository is owned by a user account rather than an organization, so the single registry maintainer is consistent with a small independently maintained project but offers limited backing capacity.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools were detected. The missing scanning is a modest repository-hygiene gap, not evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency weakness for a package intended for application integration.