Detect Weaverse

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

• JavaScript globals

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

• __weaverses

Establishes

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

Does not establish

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

Can PluginView detect Weaverse without logging in?

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

What category is Weaverse?

Weaverse is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Weaverse?

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

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