| 3 | | For example, consider the Hello Dolly plugin, which is included by default in WordPress and hasn’t been updated in 12 months. This would result in every new WordPress user encountering a "security" warning after a fresh installation, which is far from ideal. Imagine setting up WordPress for the first time and being met with a security alert. A two-year threshold would be more reasonable, in my opinion. However, setting such a threshold could lead users to believe that it applies universally to all plugins, causing them to think it’s acceptable to install a plugin that hasn’t been updated for, say, 18 months, even though this is not a straightforward matter and should be assessed on a case-by-case basis. |
| | 3 | For example, consider the Hello Dolly plugin, which is included by default in WordPress and hasn’t been updated in 12 months. This would result in every new WordPress user encountering a "security" warning after a fresh installation, which is far from ideal. Imagine setting up WordPress for the first time and being met with a security alert. A longer threshold would be more reasonable, in my opinion, however, setting such a threshold could lead users to believe that it applies universally to all plugins, causing them to think it’s acceptable to install a plugin that hasn’t been updated for, say, 18 months, even though this is not a straightforward matter and should be assessed on a case-by-case basis. |