> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mainwp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What does "Possibly Abandoned" mean?

> MainWP checks the last updated status of plugins and themes and alerts you if they haven't been updated within a threshold (default 365 days). This helps identify potentially abandoned plugins or themes.

MainWP marks plugins and themes as "Possibly Abandoned" when their last-updated date exceeds your configured tolerance. The default is 365 days. This is a prompt to investigate the item's maintenance status, not proof that its author has stopped development.

## Why This Matters

Abandoned plugins and themes can create problems for your sites:

| Risk | Impact |
| - | - |
| Security vulnerabilities | No patches for discovered security issues |
| Compatibility issues | May break with newer WordPress or PHP versions |
| Missing features | No improvements or bug fixes |
| Support unavailable | Developer may no longer provide assistance |

## How MainWP Detects Abandonment

MainWP checks the last-updated date on wordpress.org for each plugin and theme. If no update has been released within your configured threshold, the item is flagged as possibly abandoned.

<Note>
  WordPress.org dates are the default source. Items without usable dates can be checked with the optional local-file fallback described below.
</Note>

### Local File Date Fallback in 6.3

MainWP Dashboard 6.3 adds **Abandoned check by local file date** under **top-right user menu > MainWP Settings > General Settings > Updates Settings** (`/wp-admin/admin.php?page=Settings`). It is disabled by default and requires MainWP Child 6.3 or later. Enable it, save settings, and sync the affected sites before checking again.

When WordPress.org cannot provide a usable last-updated date, MainWP Child compares a local file's modification date with **Abandoned plugins/themes tolerance**:

* Plugins use their main plugin file.
* Themes use `style.css`.

This can cover premium, custom, private, or delisted items. The file must exist and be readable. A usable WordPress.org date takes priority; the fallback does not replace it.

Locally detected rows describe the age of the file modification. Copying, restoring, or deploying files can change this date without a new author release. Review the vendor's maintenance information before deciding the item is abandoned.

## Where to View Abandoned Items

Find abandoned items at:

* **Sites > Plugins > Abandoned Plugins** (`/wp-admin/admin.php?page=PluginsAbandoned`)
* **Sites > Themes > Abandoned Themes** (`/wp-admin/admin.php?page=ThemesAbandoned`)

## What to Do with Abandoned Items

1. **Assess the risk** - Consider if the plugin is critical and if alternatives exist
2. **Check GitHub** - Some plugins have active development on GitHub even without wordpress.org updates
3. **Find alternatives** - Search for actively maintained replacements
4. **Plan migration** - Replace abandoned items before they cause issues

## Adjust the Threshold

To change the number of days or disable this check, see [How to change tolerance for Abandoned Plugins and Themes](/sites/updates/how-to-change-tolerance-for-abandoned-plugins-and-themes).

***

## Related Resources

* [Check for Abandoned Plugins and Themes](/sites/plugins/check-for-abandoned-plugins-and-themes) - Manual abandonment checks
* [Change Abandoned Tolerance](/sites/updates/how-to-change-tolerance-for-abandoned-plugins-and-themes) - Adjust the threshold


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.