Sign in

Evidencenormalize-url-149

sortQueryParameters encodes the query string

normalize-url#149, at commit 6ea4038. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
REPRODUCED_AND_DIAGNOSED
Wall time
136.6s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
sindresorhus/normalize-url
Issue
#149
Pinned commit
6ea4038783d298d499583db07a820e5ca8ff2721

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

normalize-url#149 · as filedcommit 6ea4038

sortQueryParameters encodes the query string

Is it supposed to be like this?

**sortQueryParameters: true**

```js
normalizeUrl('http://sindresorhus.com/?url=http://example.com', {
    sortQueryParameters: true
});
//=> 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com'
```

**sortQueryParameters: false**

```js
normalizeUrl('http://sindresorhus.com/?url=http://example.com', {
    sortQueryParameters: false
});
//=> 'http://sindresorhus.com/?url=http://example.com'
```
Issue
#149
Commit
6ea4038783d298d499583db07a820e5ca8ff2721
Why this commit
The first parent of the fix commit c42f53bb05ec6666514580107925207ff54ad8d0, which GitHub binds to this issue via CROSS_REFERENCED_PR. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
normalizeUrl('http://sindresorhus.com/?url=http://example.com', { sortQueryParameters: true }) produces 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com'; the fix makes it produce 'http://sindresorhus.com/?url=http://example.com'.
Expression
normalizeUrl('http://sindresorhus.com/?url=http://example.com', { sortQueryParameters: true })
Reported output
'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com'
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `normalizeUrl('http://sindresorhus.com/?url=http://example.com', { sortQueryParameters: true }); //=> 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com'`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`normalizeUrl('http://sindresorhus.com/?url=http://example.com', {
sortQueryParameters: true
})` still produces 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com' (read http://sindresorhus.com/?url=http%3A%2F%2Fexample.com)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`normalizeUrl('http://sindresorhus.com/?url=http://example.com', { sortQueryParameters: true })` still produces 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com' (read http://sindresorhus.com/?url=http%3A%2F%2Fexample.com)
right-failurepassReproduced the reported failure: normalizeUrl('http://sindresorhus.com/?url=http://example.com', { sortQueryParameters: true }) produces 'http://sindresorhus.com/?url=http%3A%2F%2Fexample.com'; the fix makes it produce 'http://sindresorhus.com/?url=http://example.com'.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 6ea4038, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/sindresorhus/normalize-url
git checkout 6ea4038783d298d499583db07a820e5ca8ff2721
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases