Detect BugHerd

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

• Script sources
• JavaScript globals

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

• .bugherd.com/
• BugHerdConfig

Establishes

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

Does not establish

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

Can PluginView detect BugHerd without logging in?

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

What category is BugHerd?

BugHerd is classified under Issue trackers in the PluginView directory.

How many fingerprint rules cover BugHerd?

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 BugHerd?

Illustrative public indicators for BugHerd include .bugherd.com/; BugHerdConfig. A live scan may match additional proprietary rules beyond these examples.