Detect USWDS

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

• Script sources
• JavaScript globals

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

• \buswds\b
• uswdsPresent

Establishes

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

Does not establish

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

Can PluginView detect USWDS without logging in?

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

What category is USWDS?

USWDS is classified under UI frameworks in the PluginView directory.

How many fingerprint rules cover USWDS?

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

What public signals suggest a site uses USWDS?

Illustrative public indicators for USWDS include \buswds\b; uswdsPresent. A live scan may match additional proprietary rules beyond these examples.