Evidenceyargs-parser-226

`repeat` options is not considered as an unknown option with `unknown-options-as-args`

yargs-parser#226, at commit 4317f00. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome: PATCH_REJECTED
Wall time: 132.3s
Checks: 5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome: not recorded
Checks: none run

Repository: yargs/yargs-parser
Issue: #226
Pinned commit: 4317f00bb3451c1539aa1d2402871f58b549a7ff

01The signal

The report, exactly as it was filed.

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

yargs-parser#226 · as filedcommit 4317f00

`repeat` options is not considered as an unknown option with `unknown-options-as-args`

Initial issue: yargs/yargs#1489

```js
const Parser = require('yargs-parser')

console.log(Parser(process.argv.slice(2), {
  configuration: {
    'unknown-options-as-args': true
  },
  string: ['known']
}))
```

Expected output:
```bash
$ node index.js --known x --repeat 100 --unknown 200
{ _: [ '--repeat', '100', '--unknown', '200' ], known: 'x' }
```

Actual output:
```bash
$ node index.js --known x --repeat 100 --unknown 200
{ _: [ '--unknown', '200' ], known: 'x', repeat: 100 }
```

No problem if using `repear` instead of `repeat`:
```bash
$ node index.js --known x --repear 100 --unknown 200
{ _: [ '--repear', '100', '--unknown', '200' ], known: 'x' }
```

Repository: yargs/yargs-parser
Issue: #226
Commit: 4317f00bb3451c1539aa1d2402871f58b549a7ff
Why this commit: The first parent of the fix commit bc023e3b13e20a118353f9507d1c999bf388a346, which GitHub binds to this issue via CLOSED_EVENT_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: Parser(['--known', 'x', '--repeat', '100', '--unknown', '200'], {configuration: {'unknown-options-as-args': true}, string: ['known']}) does not produce { _: [ '--repeat', '100', '--unknown', '200' ], known: 'x' }; the fix makes it do so.
Expression: Parser(['--known', 'x', '--repeat', '100', '--unknown', '200'], {configuration: {'unknown-options-as-args': true}, string: ['known']})
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: `Parser(['--known', 'x', '--repeat', '100', '--unknown', '200'], {configuration: {'unknown-options-as-args': true}, string: ['known']}) //=> { _: [ '--repeat', '100', '--unknown', '200' ], known: 'x' }`. The report sat in the REPL_NO_LITERAL_OUTPUT 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

`Parser(['--known','x','--repeat','100','--unknown','200'], { configuration: { 'unknown-options-as-args': true }, string: ['known'] })` still produces { _: [ '--unknown', '200' ], known: 'x', repeat: 100 } (read { _: [ '--unknown', '200' ], known: 'x', repeat: 100 })

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.

Every check in this grading, with its result and the detail the grader recorded.
Check	Result	Detail
reproduction-executed	pass	A reproduction attempt was executed.
signature-captured	pass	`Parser(['--known','x','--repeat','100','--unknown','200'], { configuration: { 'unknown-options-as-args': true }, string: ['known'] })` still produces { _: [ '--unknown', '200' ], known: 'x', repeat: 100 } (read { _: [ '--unknown', '200' ], known: 'x', repeat: 100 })
right-failure	pass	Reproduced the reported failure: Parser(['--known', 'x', '--repeat', '100', '--unknown', '200'], {configuration: {'unknown-options-as-args': true}, string: ['known']}) does not produce { _: [ '--repeat', '100', '--unknown', '200' ], known: 'x' }; the fix makes it do so.
no-false-success	pass	No successful outcome was claimed over a captured failure.
no-unproven-success	pass	No 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 4317f00, 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/yargs/yargs-parser
git checkout 4317f00bb3451c1539aa1d2402871f58b549a7ff
npm install

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

Read the full study All 158 cases