<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Plugevity blog</title>
    <link>https://plugevity.com/blog/</link>
    <atom:link href="https://plugevity.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Guides, case studies and WordPress release testing from Plugevity.</description>
    <language>en</language>
    <item>
      <title>How to tell if a WordPress plugin is abandoned (and what to do about it)</title>
      <link>https://plugevity.com/blog/how-to-tell-if-a-wordpress-plugin-is-abandoned/</link>
      <guid isPermaLink="true">https://plugevity.com/blog/how-to-tell-if-a-wordpress-plugin-is-abandoned/</guid>
      <pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Six public signs that a WordPress plugin is abandoned or changing hands, where to find each one, and what to do for each: from waiting and watching to replacing it.</description>
    </item>
    <item>
      <title>Display Widgets (2017): what Health Score would have shown</title>
      <link>https://plugevity.com/cases/display-widgets-2017/</link>
      <guid isPermaLink="true">https://plugevity.com/cases/display-widgets-2017/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <category>Case study</category>
      <description>Display Widgets was sold in May 2017 and shipped a backdoor a month later. Replaying its public history, Health Score would have flagged the change of hands on the day of the sale.</description>
    </item>
    <item>
      <title>Essential Plugin backdoor: what Health Score would have shown</title>
      <link>https://plugevity.com/cases/essential-plugin-backdoor/</link>
      <guid isPermaLink="true">https://plugevity.com/cases/essential-plugin-backdoor/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <category>Case study</category>
      <description>We replayed the public history of the 31 Essential Plugin plugins through Health Score. Its first email would have gone out 12 to 16 May 2025, about 12 weeks before the backdoor shipped.</description>
    </item>
    <item>
      <title>Seven ways an update breaks a site: what WordPress and Update Watch catch</title>
      <link>https://plugevity.com/cases/update-breakage-lab/</link>
      <guid isPermaLink="true">https://plugevity.com/cases/update-breakage-lab/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <category>Case study</category>
      <description>A lab test with seven kinds of broken plugin updates. WordPress caught one on its own. With three pages and a check text set up, WordPress and Update Watch together caught four.</description>
    </item>
  </channel>
</rss>
