Detect Ractive.js

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

• Script sources

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

• ractive/ractive.min.js

Establishes

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

Does not establish

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

Can PluginView detect Ractive.js without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Ractive.js — typically script sources. It does not bypass authentication or paywalls.

What category is Ractive.js?

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

How many fingerprint rules cover Ractive.js?

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

What public signals suggest a site uses Ractive.js?

Illustrative public indicators for Ractive.js include ractive/ractive.min.js. A live scan may match additional proprietary rules beyond these examples.