Detect StatusCast

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

• JavaScript globals

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

• statuscast.libs.datatables
• statuscast.ui

Establishes

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

Does not establish

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

Can PluginView detect StatusCast without logging in?

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

What category is StatusCast?

StatusCast is classified under Issue trackers in the PluginView directory.

How many fingerprint rules cover StatusCast?

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

What public signals suggest a site uses StatusCast?

Illustrative public indicators for StatusCast include statuscast.libs.datatables; statuscast.ui. A live scan may match additional proprietary rules beyond these examples.