{"id":171697,"date":"2018-04-27T13:00:03","date_gmt":"2018-04-27T13:00:03","guid":{"rendered":"https:\/\/premium.wpmudev.org\/blog\/?p=171697"},"modified":"2018-04-24T16:41:11","modified_gmt":"2018-04-24T16:41:11","slug":"is-that-wordpress-plugin-safe-15-warning-signs-to-skip-downloading","status":"publish","type":"post","link":"https:\/\/wpmudev.com\/blog\/is-that-wordpress-plugin-safe-15-warning-signs-to-skip-downloading\/","title":{"rendered":"Is That WordPress Plugin Safe? Warning Signs to Skip Downloading"},"content":{"rendered":"

Even the smallest and simplest of WordPress websites needs plugins. Akismet is a must if the site has a blog. A security plugin like Defender<\/a> is non-negotiable. And a solid contact form<\/a> is needed if you intend on collecting leads.<\/p>\n

For the most part, though, we know that these commonly used and referenced WordPress plugins are safe. They come with millions of downloads, high ratings, and plugin developers who\u2019ve worked hard to build a positive reputation in the community by creating error-free plugins and providing top-notch support.<\/p>\n

But what about everything else? How do you know if that seemingly popular WordPress plugin (that would really do wonders for your site) is safe to use? With plugins, unfortunately, being responsible for a high percentage of security breaches (Wordfence<\/a> last put that number at 55.9%), it\u2019s kind of scary to think that any decision you make to use one is a dangerous gamble.<\/p>\n

What I\u2019d like to do now is talk about how you can tell if a WordPress plugin is safe. Specifically, I\u2019m going to share the warning signs you should pay attention to that will let you know when it\u2019s best to skip downloading one.<\/p>\n

Warning Signs That a WordPress Plugin Is Unsafe<\/h2>\n

I always feel bad having to put this advisory out there about WordPress plugins because, really, they\u2019re great. When they\u2019re coded well and properly managed, they can do wonderful things inside of WordPress. But that\u2019s sadly not always the case.<\/p>\n

Sometimes you get a plugin that was made by a newbie developer just hoping to make some money, but who didn\u2019t put the right amount of time into coding it. There are also times when you run into a plugin that is<\/em> coded well, but an errant line of code conflicts with another plugin and tears your whole site down in an instant. And, of course, there\u2019s always the risk of a hacker<\/a> or fake WordPress developer<\/a> getting their hands on it.<\/p>\n

So, this means you need to be extra vigilant about which ones you let inside–even if the original developer\u2019s intentions were good.<\/p>\n

In order to be diligent, you should know how to spot the warning signs of a bad WordPress plugin. First, start by using a system of checks to make sure the plugin is the right one<\/a> for your site. Then, you can start digging deeper to see if you can spot any of the warning signs.<\/p>\n

1. The Plugin Repository Looks Odd<\/h3>\n

Let\u2019s start with where you\u2019re hunting down these WordPress plugins. For instance, say you were interested in finding a plugin that adds a feature that\u2019s not too commonplace. You do a Google search for the feature (like \u201cgender reveal plugin\u201d) and the top results point you to a number of independent WordPress developer websites that claim to sell a plugin that does just that.<\/p>\n

Some warning bells should be going off in your head, in that case. While it doesn\u2019t mean that the source of the plugin can\u2019t be trusted if you get to the site and it looks like it was built in the early \u201800s and there\u2019s no way to contact the developer except through an email address at AOL\u2026 well, that\u2019s a huge red flag.<\/p>\n

In general, always look for WordPress plugins that come from reputable sources. Start with:<\/p>\n