Detect Ziggy

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

• JavaScript globals

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

• Ziggy

Establishes

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

Does not establish

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

A confirmed Ziggy match also implies these technologies are present.

LaravelInertia.js

Can PluginView detect Ziggy without logging in?

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

What category is Ziggy?

Ziggy is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover Ziggy?

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

What public signals suggest a site uses Ziggy?

Illustrative public indicators for Ziggy include Ziggy. A live scan may match additional proprietary rules beyond these examples.