aplia/ezfind

Release historydanger

The package has had no release in about 5 years, with zero releases in the last 12 months. Its five-release history shows an established package, but the prolonged release gap raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the long release gap and indicating that maintenance has stopped or become dormant.

Repo popularitycaution

The repository has zero stars and forks and one watcher, offering little independent evidence of adoption or community support. Popularity is supporting evidence, so this reinforces the maintenance concern without deciding it alone.

Repo toolingcaution

Composer and Phing provide build tooling, but no security scanning tools are configured. This is a modest transparency and maintenance-hygiene gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The otherwise traceable repository and existing build tooling partly offset this gap.