Sign in

Evidencequery-string-1

Plus signs not parsed as spaces

query-string#1, at commit 154f8e7. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PARTIALLY_VERIFIED
Wall time
64.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/query-string
Issue
#1
Pinned commit
154f8e70759de81e6710a417b0cb02785802b2ed

01The signal

The report, exactly as it was filed.

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

query-string#1 · as filedcommit 154f8e7

Plus signs not parsed as spaces

``` javascript
var qs = require('query-string');

// expected: {foo: 'c  '}
qs.parse('foo=c++')
// => {foo: 'c++'}
```
Issue
#1
Commit
154f8e70759de81e6710a417b0cb02785802b2ed
Why this commit
The first parent of the fix commit 4ae2d729f2acc862bbcb429cd5cf03d3f2ebe247, 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.parse('foo=c++') produces { foo: 'c++' }; the fix makes it produce { foo: 'c ' }.
Expression
qs.parse('foo=c++')
Reported output
{foo: 'c++'}
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `qs.parse('foo=c++') // => {foo: 'c++'}`.

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
`qs.parse('foo=c++')` still produces {foo: 'c++'} (read { foo: 'c++' })
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`qs.parse('foo=c++')` still produces {foo: 'c++'} (read { foo: 'c++' })
right-failurepassReproduced the reported failure: qs.parse('foo=c++') produces { foo: 'c++' }; the fix makes it produce { foo: 'c ' }.
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 154f8e7, 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/query-string
git checkout 154f8e70759de81e6710a417b0cb02785802b2ed
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