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://ko.wordpress.org/plugins/impact-check/#description)
 * [평가](https://ko.wordpress.org/plugins/impact-check/#reviews)
 *  [설치](https://ko.wordpress.org/plugins/impact-check/#installation)
 * [개발](https://ko.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.

## FAQ

### 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/)
를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/impact-check/)
을 [RSS](https://plugins.trac.wordpress.org/log/impact-check/?limit=100&mode=stop_on_copy&format=rss)
로 구독하세요.

## 변경이력

#### 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보다 적음**
 *  워드프레스 버전 ** 6.5 또는 그 이상 **
 *  다음까지 시험됨: **7.0.4**
 *  PHP 버전 ** 7.4 또는 그 이상 **
 *  언어
 * [English (US)](https://wordpress.org/plugins/impact-check/)
 * 태그:
 * [blocks](https://ko.wordpress.org/plugins/tags/blocks/)[content audit](https://ko.wordpress.org/plugins/tags/content-audit/)
   [maintenance](https://ko.wordpress.org/plugins/tags/maintenance/)[plugin usage](https://ko.wordpress.org/plugins/tags/plugin-usage/)
   [shortcodes](https://ko.wordpress.org/plugins/tags/shortcodes/)
 *  [고급 보기](https://ko.wordpress.org/plugins/impact-check/advanced/)

## 평점

아직 제출된 리뷰가 없습니다.

[Your review](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/)