Detect Open-Props

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

• DOM selectors

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

• link

Establishes

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

Does not establish

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

Can PluginView detect Open-Props without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Open-Props — typically dom selectors. It does not bypass authentication or paywalls.

What category is Open-Props?

Open-Props is classified under UI frameworks in the PluginView directory.

How many fingerprint rules cover Open-Props?

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

What public signals suggest a site uses Open-Props?

Illustrative public indicators for Open-Props include link. A live scan may match additional proprietary rules beyond these examples.