Title: Impact Check
Author: csytang
Published: <strong>2026 年 8 月 17 日</strong>
Last modified: 2026 年 8 月 17 日

---

搜尋外掛

![](https://s.w.org/plugins/geopattern-icon/impact-check.svg)

# Impact Check

 由 [csytang](https://profiles.wordpress.org/csytang/) 開發

[下載](https://downloads.wordpress.org/plugin/impact-check.0.1.0.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/impact-check/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/impact-check/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/impact-check/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/impact-check/#developers)

 [技術支援](https://wordpress.org/support/plugin/impact-check/)

## 外掛說明

Impact Check helps WordPress maintainers reduce uncertainty before deactivating 
a plugin. Select one active plugin and run a conservative, read-only scan for stored
content using shortcodes or server-registered blocks attributable to that plugin.

The report shows:

 * Matching content title, type, and status.
 * Exact shortcode tags and block names with occurrence counts.
 * Native Edit and View links when the current user has permission.
 * Attribution and scan coverage so limitations remain visible.

Impact Check is designed for agencies, freelancers, and technical site owners working
on inherited or plugin-heavy sites. It uses the active WordPress runtime registries
and local content, which lets it start from the plugin rather than requiring you
to know a shortcode or block name first.

#### Important limitations

An empty report does not prove that a plugin is unused or safe to deactivate. The
scan does not inspect plugin data, settings, widgets, hooks, templates, client-only
blocks, custom tables, metadata, files, network-active plugins, themes, mu-plugins,
or remote integrations. Oversized or otherwise skipped content makes a scan incomplete.

The plugin never deactivates plugins, changes content, or makes a deactivation recommendation.
Use a backup or staging site and your normal change-control process before modifying
a production site.

#### Privacy and external services

Impact Check runs locally on your WordPress site. It has no telemetry, tracking,
external service, account requirement, cookies, browser storage, or outbound network
request. Results exist only for the current page session, and the plugin creates
no options, metadata, custom tables, files, or logs.

## 安裝方式

 1. Upload the `impact-check` folder to `/wp-content/plugins/`, or install Impact Check
    through the WordPress Plugins screen when available.
 2. Activate the plugin.
 3. Open **Tools > Impact Check**.
 4. Select one active plugin and choose **Run read-only scan**.
 5. Review the matches and the coverage warning before planning any site change.

## 常見問題集

### Does a zero-result scan mean I can safely deactivate the selected plugin?

No. It means no matches were found within the explicitly stated coverage. The selected
plugin may still affect data, settings, widgets, hooks, templates, client-only blocks,
metadata, files, custom tables, scheduled tasks, or remote integrations.

### Does Impact Check change or render my content?

No. It reads eligible stored content in bounded batches and uses WordPress parsing
functions to count exact attributed identifiers. It does not execute shortcodes,
render blocks, edit content, or change another plugin’s state.

### Which plugins can I scan?

The current version scans one active, per-site plugin selected from a server-generated
list. Network-active plugins, inactive plugins, themes, and mu-plugins are outside
the current coverage.

### Why might a shortcode or block be missing?

Impact Check only reports identifiers it can conservatively attribute to the selected
plugin from registered callback or local asset evidence. Client-only blocks, proxy
callbacks, dynamically wrapped callbacks, and registrations without attributable
source evidence can remain outside the report.

### Does the plugin send site data anywhere?

No. There are no external services or outbound requests. The administrator’s browser
sends authenticated, same-origin scan batches only to that site’s WordPress AJAX
endpoint.

## 使用者評論

這個外掛目前沒有任何使用者評論。

## 參與者及開發者

以下人員參與了開源軟體〈Impact Check〉的開發相關工作。

參與者

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

[將〈Impact Check〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/impact-check)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/impact-check/)、
查看 [SVN 存放庫](https://plugins.svn.wordpress.org/impact-check/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/impact-check/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/impact-check/)。

## 變更記錄

#### 0.1.0

 * Initial free release.
 * Added plugin-first attribution for registered shortcodes and server-registered
   blocks.
 * Added bounded, read-only stored-content scanning with capability-safe result 
   links.
 * Added explicit limitations and incomplete-scan handling.

## 中繼資料

 *  版本 **0.1.0**
 *  最後更新 **2 週前**
 *  啟用安裝數 **少於 10 次**
 *  WordPress 版本需求 ** 6.5 或更新版本 **
 *  已測試相容的 WordPress 版本 **7.0.4**
 *  PHP 版本需求 ** 7.4 或更新版本 **
 *  語言
 * [English (US)](https://wordpress.org/plugins/impact-check/)
 * 標籤:
 * [blocks](https://tw.wordpress.org/plugins/tags/blocks/)[content audit](https://tw.wordpress.org/plugins/tags/content-audit/)
   [maintenance](https://tw.wordpress.org/plugins/tags/maintenance/)[plugin usage](https://tw.wordpress.org/plugins/tags/plugin-usage/)
   [shortcodes](https://tw.wordpress.org/plugins/tags/shortcodes/)
 *  [進階檢視](https://tw.wordpress.org/plugins/impact-check/advanced/)

## 評分

這個項目尚無任何評論記錄。

[撰寫評分](https://wordpress.org/support/plugin/impact-check/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/impact-check/reviews/)

## 參與者

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

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/impact-check/)