Detect Cleave.js

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

• Script sources

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

• cleave.min?.x?.js?ver=0.0?

Establishes

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

Does not establish

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

Can PluginView detect Cleave.js without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Cleave.js — typically script sources. It does not bypass authentication or paywalls.

What category is Cleave.js?

Cleave.js is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover Cleave.js?

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

What public signals suggest a site uses Cleave.js?

Illustrative public indicators for Cleave.js include cleave.min?.x?.js?ver=0.0?. A live scan may match additional proprietary rules beyond these examples.