Detect Cargo

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

• Script sources
• JavaScript globals
• DOM selectors

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

• ?<!elo.io/cargo.
• Cargo.Config
• CargoEditor
• __cargo_js_ver__
• link

Establishes

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

Does not establish

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

A confirmed Cargo match also implies these technologies are present.

PHP

Can PluginView detect Cargo without logging in?

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

What category is Cargo?

Cargo is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Cargo?

This reference currently tracks 5 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 Cargo?

Illustrative public indicators for Cargo include ?<!elo.io/cargo.; Cargo.Config; CargoEditor. A live scan may match additional proprietary rules beyond these examples.