Detect Koha

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

• Meta tags
• JavaScript globals
• DOM selectors
• HTML markup

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

• generator: Koha
• KOHA
• input, a
• <input name="koha_login_context" value="intranet" type="hidden">
• <a href="/cgi-bin/koha/

Establishes

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

Does not establish

A sitewide install of Koha, an active vendor contract, exclusive use, or that Koha 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 Koha signals.
2. 2. PluginView reads only public responses (meta tags, javascript globals, dom selectors) and scores them against the Koha signature set (5 rules).
3. 3. Review the confidence score and text explanation for Koha on the results page.

A confirmed Koha match also implies these technologies are present.

Perl

Can PluginView detect Koha without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Koha — typically meta tags, javascript globals, dom selectors, html markup. It does not bypass authentication or paywalls.

What category is Koha?

Koha is classified under DMS in the PluginView directory.

How many fingerprint rules cover Koha?

This reference currently tracks 5 fingerprint rules across meta tags, javascript globals, dom selectors, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Koha?

Illustrative public indicators for Koha include generator: Koha; KOHA; input, a. A live scan may match additional proprietary rules beyond these examples.