Detect Splide

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

• JavaScript globals

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

• Splide.STATES
• Splide.name: i

Establishes

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

Does not establish

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

Can PluginView detect Splide without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Splide — typically javascript globals. It does not bypass authentication or paywalls.

What category is Splide?

Splide is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover Splide?

This reference currently tracks 2 fingerprint rules across javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Splide?

Illustrative public indicators for Splide include Splide.STATES; Splide.name: i. A live scan may match additional proprietary rules beyond these examples.