Detect Glide.js

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

• Script sources
• JavaScript globals
• DOM selectors

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

• @glidejs/glide@?
• Glide
• div

Establishes

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

Does not establish

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

Can PluginView detect Glide.js without logging in?

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

What category is Glide.js?

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

How many fingerprint rules cover Glide.js?

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

What public signals suggest a site uses Glide.js?

Illustrative public indicators for Glide.js include @glidejs/glide@?; Glide; div. A live scan may match additional proprietary rules beyond these examples.