/**
 * Optional URL scrubbing — `scrubQueryStrings: true`. **Off by default.**
 *
 * Query strings are where secrets end up: real applications put password-reset
 * tokens, magic-link codes, invite codes and email addresses in them, and
 * telemetry storage is permanent. So this exists.
 *
 * But it was the default once and that was wrong. The query and the fragment are
 * usually the only place the URL says *which thing* — `?workflow=42`, or a hash
 * route like `#/workflows/42/runs/abc`, where the fragment IS the route. With it
 * on, "which workflow was the user on when this broke" has no answer, and that
 * question is most of the value of browser telemetry. Secrets in URLs are worth
 * fixing at the source; a route you never recorded is not recoverable at all.
 *
 * When it is on: the path survives, the query and the fragment are dropped, and
 * the fact that something was dropped is recorded rather than silently erased, so
 * nobody debugging a route mismatch wonders whether a URL ever had parameters.
 */
/**
 * Drop the query and fragment from one URL, leaving a marker when either was
 * present. Anything that doesn't parse as an http(s) URL is returned untouched —
 * this must never mangle a value it doesn't understand.
 */
export declare function stripQuery(value: string): string;
/**
 * Rewrite the URL-shaped attributes of one span in place. Returns the number of
 * values changed, which the debug log reports so the behaviour is observable
 * rather than mysterious.
 */
export declare function scrubAttributes(attributes: Record<string, unknown>, transform?: (value: string) => string): number;
//# sourceMappingURL=scrub.d.ts.map