Detect ARM JS

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

• JavaScript globals

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

• ARM.aliases

Establishes

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

Does not establish

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

Can PluginView detect ARM JS without logging in?

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

What category is ARM JS?

ARM JS is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover ARM JS?

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 ARM JS?

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