Detect Aurelia

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

• Script sources
• JavaScript globals
• DOM selectors

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

• aurelia.js
• _aureliaConfigureModuleLoader
• localAurelia
• div, body, a

Establishes

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

Does not establish

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

Can PluginView detect Aurelia without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Aurelia — typically script sources, javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is Aurelia?

Aurelia is classified under JavaScript frameworks in the PluginView directory.

How many fingerprint rules cover Aurelia?

This reference currently tracks 4 fingerprint rules across script sources, javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Aurelia?

Illustrative public indicators for Aurelia include aurelia.js; _aureliaConfigureModuleLoader; localAurelia. A live scan may match additional proprietary rules beyond these examples.