Title: Umiushi Lab – Find Code That Updates Don&#8217;t Reach
Author: umiushilab
Published: <strong>November 16, 2026</strong>
Last modified: November 16, 2026

---

Search plugins

![](https://ps.w.org/umiushi-unreached-updates/assets/banner-772x250.png?rev=3804236)

![](https://ps.w.org/umiushi-unreached-updates/assets/icon-256x256.png?rev=3804236)

# Umiushi Lab – Find Code That Updates Don’t Reach

 By [umiushilab](https://profiles.wordpress.org/umiushilab/)

[Download](https://downloads.wordpress.org/plugin/umiushi-unreached-updates.0.1.2.zip)

 * [Details](https://wordpress.org/plugins/umiushi-unreached-updates/#description)
 * [Reviews](https://wordpress.org/plugins/umiushi-unreached-updates/#reviews)
 *  [Installation](https://wordpress.org/plugins/umiushi-unreached-updates/#installation)
 * [Development](https://wordpress.org/plugins/umiushi-unreached-updates/#developers)

 [Support](https://wordpress.org/support/plugin/umiushi-unreached-updates/)

## Description

The Updates screen tells you when WordPress, or a plugin or theme from WordPress.
org, has a new version waiting. Some code on a site is outside that: a plugin that
was closed on WordPress.org, a plugin whose newer version needs a newer WordPress
than the site runs, and themes or plugins that were built for the site or bought
elsewhere. This plugin lists that code and shows where it can be reached from outside.

 * **Finds the code that does not come from WordPress.org.** Your active theme, 
   your plugins and your must-use plugins are compared with what WordPress already
   knows from its update checks.
 * **Counts the ways in from outside.** Page templates, background requests (`wp_ajax_`,`
   admin_post_`), REST routes, shortcodes, hooks that read the request on every 
   page, and PHP files that do work when their address is opened directly.
 * **Marks the ones to look at first.** Entries that take outside input where no
   login, permission or nonce check is visible in the same file. REST routes open
   to everyone.
 * **Shows the rest of the house in one picture.** PHP support status, waiting updates,
   plugins that are installed but switched off, programs in the uploads folder, 
   leftover files, and a few settings.
 * **Says why waiting updates are still waiting.** For each waiting plugin and theme
   update: will it install on its own? And which setting holds updates back: automatic
   updates switched off, file changes refused, a site under version control, a server
   where WordPress cannot write its files, the scheduler switched off, or an update
   that needs a newer PHP.
 * **Asks WordPress.org about updates that do not reach you.** Plugins that were
   closed on WordPress.org, plugins whose newer version needs a newer WordPress 
   than yours (the Updates screen never shows those), and plugins that had no release
   for two years.

#### What it does not do

It does not tell you whether an entry is actually weak. A map shows where to look;
deciding takes reading the code. The screen says so, and never shows “safe” or “
no problem” for custom code.

It does not change anything on your site.

#### Privacy

The map is made inside your site. No code and no site data are sent anywhere. Folder
names of installed plugins are sent to WordPress.org, as described next.

The only outside request starts when an administrator presses “Map this site” or“
Ask WordPress.org again”; the screen says so next to the button. It sends the folder
names (slugs) of your installed plugins to `api.wordpress.org`, the same service
WordPress itself asks for updates. See “External services” below.

#### Paid service by the author

Reading custom code entry by entry, reporting what a stranger could see or change,
and repairing small weaknesses after the owner approves each change is a separate,
paid service by Umiushi Lab. This plugin works without it and does not install or
download anything from it. The result screen has one link to the author’s site: 
https://umiushi-lab.com/en/

### External services

This plugin connects to the WordPress.org Plugin API (`https://api.wordpress.org/
plugins/info/1.2/`) to learn whether plugins installed on your site were closed,
have a newer version that your WordPress version cannot receive, or have not been
updated for two years.

 * It is used only when an administrator presses the “Map this site” or “Ask WordPress.
   org again” button. The screen states what is sent before the first press.
 * It sends the folder name (slug) of each installed plugin (at most 60 per press),
   one request per plugin. No other data is sent.
 * The service is provided by WordPress.org: [terms](https://wordpress.org/about/tos/),
   [privacy policy](https://wordpress.org/about/privacy/).

## Screenshots

[⌊The map of a site: the code that WordPress.org does not update, how many ways 
in it has, and the whole site drawn as a house, part by part.⌉⌊The map of a site:
the code that WordPress.org does not update, how many ways in it has, and the whole
site drawn as a house, part by part.⌉[

The map of a site: the code that WordPress.org does not update, how many ways in
it has, and the whole site drawn as a house, part by part.

[⌊Why waiting updates are still waiting, and every way into a custom plugin, with
the ones that take outside input and show no login or permission check marked first.⌉⌊
Why waiting updates are still waiting, and every way into a custom plugin, with 
the ones that take outside input and show no login or permission check marked first
.⌉[

Why waiting updates are still waiting, and every way into a custom plugin, with 
the ones that take outside input and show no login or permission check marked first.

## Installation

 1. Upload the plugin folder to `/wp-content/plugins/`, or install it from the Plugins
    screen.
 2. Activate it.
 3. Open “Unreached Updates” in the admin menu and press “Map this site”.

## FAQ

### Does it send my code anywhere?

No. It reads files on your own server and stores the counts in your database.

### It lists a plugin I bought. Is that a problem?

Not by itself. Purchased plugins are listed because WordPress.org does not review
them and does not send them updates; their own vendor does. The map shows them so
you know which code depends on someone other than WordPress.org.

### An entry says “Not seen in this file”. Is it vulnerable?

Not necessarily. The check may live in another file. The map cannot follow that;
a person has to read it (the author offers this as a paid service).

### Who can see the map?

Administrators only (`manage_options`).

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Umiushi Lab – Find Code That Updates Don’t Reach” is open source software. The 
following people have contributed to this plugin.

Contributors

 *   [ umiushilab ](https://profiles.wordpress.org/umiushilab/)

[Translate “Umiushi Lab – Find Code That Updates Don’t Reach” into your language.](https://translate.wordpress.org/projects/wp-plugins/umiushi-unreached-updates)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/umiushi-unreached-updates/),
check out the [SVN repository](https://plugins.svn.wordpress.org/umiushi-unreached-updates/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/umiushi-unreached-updates/)
by [RSS](https://plugins.trac.wordpress.org/log/umiushi-unreached-updates/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.1.2

 * Fixed a fatal error when pressing “Map this site” on servers where PHP’s GLOB_BRACE
   is not available (for example Alpine Linux and WordPress Playground).

#### 0.1.1

 * New table: “Updates that are waiting, and why”. It lists the plugin and theme
   updates that are waiting, says for each one whether it will install on its own,
   and names the settings that hold updates back: automatic updates switched off
   for the whole site or by a plugin or host, file changes refused (DISALLOW_FILE_MODS),
   a site under version control, a server where WordPress cannot write its own files,
   requests to wordpress.org blocked, the scheduler switched off, or an update that
   needs a newer PHP. All of it is read from the site itself; nothing is sent.
 * Pressing “Map this site” now also asks WordPress.org about each installed plugin,
   and the results get their own table: “Updates that do not reach this site”.
 * The WordPress.org check now also finds plugins whose newer version needs a newer
   WordPress than yours (the Updates screen never shows those), and plugins that
   were closed long ago and are no longer in WordPress’s update data. It now asks
   about every installed plugin, not only those WordPress.org is known to list.
 * Names the maintenance release of your current WordPress branch (for example 6.4.14
   for 6.4.13).
 * Translation files are no longer bundled; translations come from translate.wordpress.
   org.

#### 0.1.0

 * First version: custom code map, house overview, optional WordPress.org check 
   for abandoned plugins.

## Meta

 *  Version **0.1.2**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [attack-surface](https://wordpress.org/plugins/tags/attack-surface/)[audit](https://wordpress.org/plugins/tags/audit/)
   [custom code](https://wordpress.org/plugins/tags/custom-code/)[security](https://wordpress.org/plugins/tags/security/)
   [theme](https://wordpress.org/plugins/tags/theme/)
 *  [Advanced View](https://wordpress.org/plugins/umiushi-unreached-updates/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/umiushi-unreached-updates/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/umiushi-unreached-updates/reviews/)

## Contributors

 *   [ umiushilab ](https://profiles.wordpress.org/umiushilab/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/umiushi-unreached-updates/)