Detect StimulusReflex

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

• DOM selectors
• Inline scripts

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

• .stimulate

Establishes

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

Does not establish

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

A confirmed StimulusReflex match also implies these technologies are present.

Ruby on RailsStimulus

Can PluginView detect StimulusReflex without logging in?

Yes. PluginView only reads publicly accessible responses when checking for StimulusReflex — typically dom selectors, inline scripts. It does not bypass authentication or paywalls.

What category is StimulusReflex?

StimulusReflex is classified under Web frameworks in the PluginView directory.

How many fingerprint rules cover StimulusReflex?

This reference currently tracks 2 fingerprint rules across dom selectors, inline scripts. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses StimulusReflex?

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