Title: Kistn API Client
Author: Christian Doebler
Published: <strong>2026년 7월 1일</strong>
Last modified: 2026년 7월 12일

---

플러그인 검색

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

# Kistn API Client

 작성자: [Christian Doebler](https://profiles.wordpress.org/grissi/)

[다운로드](https://downloads.wordpress.org/plugin/kistn.1.0.2.zip)

 * [세부사항](https://ko.wordpress.org/plugins/kistn/#description)
 * [평가](https://ko.wordpress.org/plugins/kistn/#reviews)
 *  [설치](https://ko.wordpress.org/plugins/kistn/#installation)
 * [개발](https://ko.wordpress.org/plugins/kistn/#developers)

 [지원](https://wordpress.org/support/plugin/kistn/)

## 설명

Collects installed plugins, themes, and WordPress core, then pushes inventory to
your Kistn server for centralized vulnerability monitoring.

**Push flow:**

 1. Preflight — asks the server which slugs need a fresh advisory check and which are
    known-private.
 2. Hash check — skips push if inventory unchanged.
 3. WPScan lookup — queries the WPScan vulnerability database only for stale, non-private
    slugs.
 4. Push — sends packages, vulnerability findings, advisory snapshots, and any newly-
    discovered private slugs.

Private packages (those absent from the WPScan database) are tracked server-side
so subsequent runs never waste WPScan quota on them. When the server later confirms
a package is public, the project owner is notified.

**Configuration** via Settings  Kistn, or via constants in wp-config.php:

define( ‘KISTN_BASE_URL’, ‘https://your-server.example.com’ );
 define( ‘KISTN_PROJECT_ID’,‘
your-project-uuid’ ); define( ‘KISTN_TOKEN’, ‘your-api-token’ ); define( ‘KISTN_WPSCAN_TOKEN’,‘
your-wpscan-api-token’ ); // optional, enables vulnerability lookups

### External services

This plugin can connect to WPScan API to obtain latest security information about
your installation. Use of this feature is optional. To use this feature, you need
a WPScan account and your own API token.

When the feature is used, this plugin sends information about installed WordPress
core, plugins and themes to retrieve latest security advisories about your installed
components. The service is provided by “WPScan”: https://wpscan.com/terms/, https://
automattic.com/privacy/.

## 설치

 1. In your WordPress admin, go to Plugins  Add New, search for “Kistn API Client”,
    install and activate.
 2. Alternatively, upload the plugin ZIP via Plugins  Add New  Upload Plugin, then 
    activate.
 3. Alternatively, via Composer: `composer require kistn/wp-client`, then activate 
    as usual.
 4. Go to Settings  Kistn and configure your API credentials.

## 후기

이 플러그인에 대한 평가가 없습니다.

## 기여자 & 개발자

“Kistn API Client”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에
기여하였습니다.

기여자

 *   [ Christian Doebler ](https://profiles.wordpress.org/grissi/)

[자국어로 “Kistn API Client”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/kistn)

### 개발에 관심이 있으십니까?

[코드 탐색하기](https://plugins.trac.wordpress.org/browser/kistn/)는, [SVN 저장소](https://plugins.svn.wordpress.org/kistn/)
를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/kistn/)을 [RSS](https://plugins.trac.wordpress.org/log/kistn/?limit=100&mode=stop_on_copy&format=rss)
로 구독하세요.

## 변경이력

#### 1.0.2

 * Fix: The settings page no longer shows “Configuration incomplete” after saving
   valid settings with the (optional) WPScan API Token left empty — the completeness
   notice now reflects the just-saved state.
 * Fix: Public plugins/themes hosted on wordpress.org are no longer mislabelled 
   as private. Public/private is now determined from wordpress.org directory membership(
   via WP’s own update transient) instead of the presence of a `PluginURI` header
   or a WPScan entry — a public plugin can lack both.
 * Change: The inventory payload now reports confirmed-public slugs in a new `public_packages`
   field so the server can display them with their public registry information.

#### 1.0.1

 * Fix: WPScan requests now pause until the next day (site timezone) after hitting
   the 429 rate limit, instead of retrying every remaining slug in the same run.
 * Change: The Push Interval field is now hidden when Schedule Mode is set to WP-
   CLI only (it doesn’t apply to that mode).
 * Change: Renamed the WP-CLI command from `wp inventory push` to `wp kistn push`.
 * Change: Added an example placeholder to the API Base URL field.
 * Docs: Documented WordPress-plugin-repository installation as the primary install
   method.
 * Change: The server-crontab hint under Settings  Kistn now toggles live when Schedule
   Mode is switched, instead of only appearing after a save.
 * Docs: Documented Composer installation option (`composer require kistn/wp-client`)
   in README.md and readme.txt.

#### 1.0.0

 * Initial release.

## 기초

 *  버전 **1.0.2**
 *  최근 업데이트: **4주 전**
 *  활성화된 설치 **10보다 적음**
 *  워드프레스 버전 ** 6.0 또는 그 이상 **
 *  다음까지 시험됨: **7.0.2**
 *  PHP 버전 ** 8.3 또는 그 이상 **
 *  언어
 * [English (US)](https://wordpress.org/plugins/kistn/)
 * 태그:
 * [inventory](https://ko.wordpress.org/plugins/tags/inventory/)[monitoring](https://ko.wordpress.org/plugins/tags/monitoring/)
   [security](https://ko.wordpress.org/plugins/tags/security/)[vulnerability](https://ko.wordpress.org/plugins/tags/vulnerability/)
 *  [고급 보기](https://ko.wordpress.org/plugins/kistn/advanced/)

## 평점

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

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

[모든  리뷰 보기](https://wordpress.org/support/plugin/kistn/reviews/)

## 기여자

 *   [ Christian Doebler ](https://profiles.wordpress.org/grissi/)

## 지원

할 말 있으신가요? 도움이 필요하신가요?

 [지원 포럼 보기](https://wordpress.org/support/plugin/kistn/)