Sign in

Evidenceqs-390

Stringify with {format: "RFC1738"}

qs#390, at commit 9c60d53. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
NO_RUNNABLE_CHECK
Wall time
351.2s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
ljharb/qs
Issue
#390
Pinned commit
9c60d5318865648ed10074b09bef04b5f04b8fda

01The signal

The report, exactly as it was filed.

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

qs#390 · as filedcommit 9c60d53

Stringify with {format: "RFC1738"}

I want to stringify a object with RFC1738 format.
As defined in RFC1738 "(" and ")" should be allowed and therefore not be encoded.
```
let urlQuery = {
  foo(ref): "BAR"
}
qs.stringify(urlQuery, { format: 'RFC1738' });
```

### Expected Result
`"foo(ref)=BAR"`

### Current Result
`"foo%28ref%29=BAR"`
Repository
ljharb/qs
Issue
#390
Commit
9c60d5318865648ed10074b09bef04b5f04b8fda
Why this commit
The first parent of the fix commit 4e7a5a38bb0332662250cee1b05fa97fc70a62d1, which GitHub binds to this issue via CLOSED_EVENT_COMMIT. 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
qs.stringify({"foo(ref)": "BAR"}, {format: "RFC1738"}) produces 'foo%28ref%29=BAR'; the fix makes it produce 'foo(ref)=BAR'.
Expression
qs.stringify({"foo(ref)": "BAR"}, {format: "RFC1738"})
Reported output
"foo%28ref%29=BAR"
Where that came from
Proposed by a model reading this report and nothing else -- it never saw the repository or the fix commit -- and read back as a claim by the same parser the harvest uses, SAME_LINE form: `qs.stringify({"foo(ref)": "BAR"}, {format: "RFC1738"}) //=> "foo%28ref%29=BAR"`. The report sat in the CODE_NO_ANNOTATION_AT_ALL bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.

03What happened

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

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-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `qs.stringify({"foo(ref)": "BAR"}, {format: "RFC1738"})` still producing "foo%28ref%29=BAR".
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 9c60d53, 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/ljharb/qs
git checkout 9c60d5318865648ed10074b09bef04b5f04b8fda
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