Evidencecamelcase-4

Edge cases

camelcase#4, at commit ca0d761. 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: 97.4s
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/camelcase
Issue: #4
Pinned commit: ca0d7611a290b9f4bfe9720fe36fa1700da13541

01The signal

The report, exactly as it was filed.

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

camelcase#4 · as filedcommit ca0d761

Edge cases

``` js
> camelCase('', '')
'-'
> camelCase(' ')
TypeError: Cannot read property 'toLowerCase' of undefined
```

I think it should return an empty string in both cases.

Repository: sindresorhus/camelcase
Issue: #4
Commit: ca0d7611a290b9f4bfe9720fe36fa1700da13541
Why this commit: The first parent of the fix commit 1a69a04a940ce56f1e8e915684091515c551ac35, 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: camelCase('', '') produces '-'; the fix makes it produce ''.
Expression: camelCase('', '')
Reported output: '-'
Where that came from: Read mechanically from the report's fenced code, REPL form: `> camelCase('', '') '-'`.

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

`camelCase('', '')` still produces '-' (read -)

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	`camelCase('', '')` still produces '-' (read -)
right-failure	pass	Reproduced the reported failure: camelCase('', '') produces '-'; the fix makes it produce ''.
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 ca0d761, 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/camelcase
git checkout ca0d7611a290b9f4bfe9720fe36fa1700da13541
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