Detect Glider.js

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

• Script sources

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

• @??/glider.min.js

Establishes

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

Does not establish

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

Can PluginView detect Glider.js without logging in?

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

What category is Glider.js?

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

How many fingerprint rules cover Glider.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 Glider.js?

Illustrative public indicators for Glider.js include @??/glider.min.js. A live scan may match additional proprietary rules beyond these examples.