Client content contains a supported non-production deployment URL
ShipReady found a supported staging or preview deployment URL in a recognised static client URL-value context.
Why it matters
A non-production endpoint in public client configuration should be reviewed before relying on it for customer traffic.
How ShipReady detects it
What it inspects
ShipReady inspects fetched executable client content and supported inline regions for maintained staging or preview URL patterns in value-like positions.
What triggers a finding
The rule triggers when a supported non-production URL appears in the scanner's recognised value context and is not a placeholder host or a supported suppressed case.
What the evidence shows
The inspected client content contains a URL value matched by ShipReady's non-production deployment heuristic.
Limits of this check
ShipReady does not request the URL, execute the code, determine whether it is in use, inspect data environments, or prove that customer traffic reaches a staging system.
How to fix it
Review the shipped endpoint configuration
Trace the value to public build configuration and replace unintended preview or staging endpoints with the intended production endpoint.
How to verify the change
Inspect the deployed client build
After deployment, verify the matched non-production URL no longer appears in the relevant client configuration.
Expected: The published client configuration contains the intended production endpoint.