How to Tell If a WordPress Plugin Is Abandoned (One Field Won't Tell You)

Описание и применение

Определение статуса поддержки плагина WordPress с помощью нескольких сигналов из каталога, включая дату последнего обновления, тестирование, закрытие и поддержку.

Задача

Determining whether a WordPress plugin is abandoned or still maintained using available directory data.

Результат

By aggregating multiple directory signals, users can reliably determine plugin maintenance status and avoid relying on a single field.

Рабочий процесс

• Query plugin info via WordPress API endpoint
• Extract fields: version, last_updated, tested, requires_php, active_installs, support_threads, support_threads_resolved
• Check for closed:true and reason field
• Interpret last_updated: <6 months = maintained, 6-11 months = watch, 12-23 months = ageing, 24+ months = unmaintained (large plugins)
• Assess tested field: stale if not updated with latest 3 WP releases
• Evaluate closed reason: security-issue = replace, author-request = check author site
• Consider support_threads ratio cautiously; verify recent author replies
• Identify premium plugins outside directory; verify license status
• Combine signals per table to decide plugin health
• Optional: run provided Node script to batch-check multiple plugins

Доказательства

The last release date is the strongest signal.

Источник

The "tested" field is the author telling you the newest WordPress version they checked the plugin against.

Источник

For author-request closures, the next step is to check the author's own site or repository for recent releases.

Источник

Premium plugins usually only get updates while the licence is active.

Источник