Detect Lightning

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

• Script sources
• JavaScript globals
• DOM selectors

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

• wp-content/themes/lightning-pro?/.lightning.min.js.ver=?
• lightningOpt.header_scrool
• link, link

Establishes

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

Does not establish

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

Can PluginView detect Lightning without logging in?

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

What category is Lightning?

Lightning is classified under WordPress themes in the PluginView directory.

How many fingerprint rules cover Lightning?

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 Lightning?

Illustrative public indicators for Lightning include wp-content/themes/lightning-pro?/.lightning.min.js.ver=?; lightningOpt.header_scrool; link, link. A live scan may match additional proprietary rules beyond these examples.