Detect autoComplete.js

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

• Script sources

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

• @tarekraafat/autocomplete.js@/

Establishes

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

Does not establish

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

Can PluginView detect autoComplete.js without logging in?

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

What category is autoComplete.js?

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

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

Illustrative public indicators for autoComplete.js include @tarekraafat/autocomplete.js@/. A live scan may match additional proprietary rules beyond these examples.