Sign in

Evidencecookie-21

Overeager parsing

cookie#21, at commit faf3895. 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
69.5s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
jshttp/cookie
Issue
#21
Pinned commit
faf389539824d5c973e4d9604ce89089941d820b

01The signal

The report, exactly as it was filed.

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

cookie#21 · as filedcommit faf3895

Overeager parsing

[`/[;,] */`](https://github.com/defunctzombie/node-cookie/blob/master/index.js#L34) is too aggressive (it should be changed to just `/; *`, otherwise it fails on `toUTCString` strings:

``` js
cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/')
--> {Path: '/', expires: 'Wed'}
```
Repository
jshttp/cookie
Issue
#21
Commit
faf389539824d5c973e4d9604ce89089941d820b
Why this commit
The first parent of the fix commit 6d7db5f265c2eea5314ed047ebfb737290e9c2d8, 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
cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/') produces { Path: '/', expires: 'Wed' }; the fix makes it produce { Path: '/', expires: 'Wed, 29 Jan 2014 17:43:25 GMT' }.
Expression
cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/')
Reported output
{Path: '/', expires: 'Wed'}
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: `cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/') //=> {Path: '/', expires: 'Wed'}`. The report sat in the NO_FENCE_INLINE_CODE_ONLY bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.

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
`cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/')` still produces {Path: '/', expires: 'Wed'} (read { expires: 'Wed', Path: '/' })
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`cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/')` still produces {Path: '/', expires: 'Wed'} (read { expires: 'Wed', Path: '/' })
right-failurepassReproduced the reported failure: cookie.parse('expires=Wed, 29 Jan 2014 17:43:25 GMT; Path=/') produces { Path: '/', expires: 'Wed' }; the fix makes it produce { Path: '/', expires: 'Wed, 29 Jan 2014 17:43:25 GMT' }.
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 faf3895, 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/jshttp/cookie
git checkout faf389539824d5c973e4d9604ce89089941d820b
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