Detect Page.js

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

• JavaScript globals

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

• page.Route

Establishes

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

Does not establish

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

Can PluginView detect Page.js without logging in?

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

What category is Page.js?

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

How many fingerprint rules cover Page.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 Page.js?

Illustrative public indicators for Page.js include page.Route. A live scan may match additional proprietary rules beyond these examples.