Detect Koishi.js

PluginView evaluates public page signals in these classes when identifying Koishi.js. Individual fingerprint rule bodies are proprietary and are not published.

• JavaScript globals

Illustrative indicators derived from public catalog metadata for Koishi.js. A live scan may match additional proprietary rules beyond these examples.

• KOISHI_CONFIG

Establishes

One or more public signals on the scanned page matched a known Koishi.js signature (1 rules) at the time of the scan.

Does not establish

A sitewide install of Koishi.js, an active vendor contract, exclusive use, or that Koishi.js is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Koishi.js signals.
2. 2. PluginView reads only public responses (javascript globals) and scores them against the Koishi.js signature set (1 rules).
3. 3. Review the confidence score and text explanation for Koishi.js on the results page.

A confirmed Koishi.js match also implies these technologies are present.

TypeScript

Can PluginView detect Koishi.js without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Koishi.js — typically javascript globals. It does not bypass authentication or paywalls.

What category is Koishi.js?

Koishi.js is classified under JavaScript frameworks in the PluginView directory.

How many fingerprint rules cover Koishi.js?

This reference currently tracks 1 fingerprint rule across javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Koishi.js?

Illustrative public indicators for Koishi.js include KOISHI_CONFIG. A live scan may match additional proprietary rules beyond these examples.