Detect OpenUI5

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

• Cookies
• Script sources
• JavaScript globals

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

• sap-usercontext: sap-client
• sap-ui-core.js
• sap.ui.version: .

Establishes

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

Does not establish

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

Can PluginView detect OpenUI5 without logging in?

Yes. PluginView only reads publicly accessible responses when checking for OpenUI5 — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is OpenUI5?

OpenUI5 is classified under JavaScript frameworks, UI frameworks in the PluginView directory.

How many fingerprint rules cover OpenUI5?

This reference currently tracks 3 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses OpenUI5?

Illustrative public indicators for OpenUI5 include sap-usercontext: sap-client; sap-ui-core.js; sap.ui.version: .. A live scan may match additional proprietary rules beyond these examples.