Evidencecamelcase-77

Converting either volume_3d or volume3d results in volume3D making it impossible to decamelize

camelcase#77, at commit 20591fb. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome: REPRODUCED_AND_DIAGNOSED
Wall time: 130.2s
Checks: 5 passed of 5 applicable

RECORDED

WRONG_FAILURE

graded from the transcript committed with this case.

Outcome: INCONCLUSIVE
Wall time: 0.7s
Checks: 4 passed of 5 applicable

Repository: sindresorhus/camelcase
Issue: #77
Pinned commit: 20591fbda80c5c15e446766e877530f00ec1c5d1

01The signal

The report, exactly as it was filed.

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

camelcase#77 · as filedcommit 20591fb

Converting either volume_3d or volume3d results in volume3D making it impossible to decamelize

How to reproduce:
```
console.log(camelcase('volume_3d')); // volume3D
console.log(camelcase('volume3d')); // volume3D
```

this operates under the assumption that decamelizing should return the string to its original decamelized version but I'm not sure how that would be possible for strings in this format.

Repository: sindresorhus/camelcase
Issue: #77
Commit: 20591fbda80c5c15e446766e877530f00ec1c5d1
Why this commit: The fix commit's parent where the closing commit was identifiable in the repository, otherwise the commit that was HEAD of the default branch at the moment the issue was filed. fixCommit deliberately LEFT UNBOUND 2026-08-26. Issue #77 was closed 2023-08-09T16:30:09Z, two seconds after PR #112 ('Removing casing to characters after a number that are followed by a separator (issue #77)', squash-merged as e7dccc90) -- so the obvious binding is e7dccc90, and it is wrong. MEASURED by importing index.js at e7dccc90 and at its parent: camelcase('volume_3d') is 'volume3D' before AND after, and camelcase('volume3d') is 'volume3D' before AND after. What e7dccc90 changes is 'b2b_registration_request', which is a different string in a different comment on the same thread. MEASURED at origin/main (9.0.0): both of the reporter's expressions still return 'volume3D'. The reported defect was never fixed; the later `capitalizeAfterNumber` option is opt-in and does not change the default. There is no fix commit to bind.
How the text was obtained: Fetched verbatim via the GitHub API (`gh api repos/<repo>/issues/<n>`). Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain: javascript · node · ava · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case

Symptom: camelcase('volume_3d') and camelcase('volume3d') both return 'volume3D'.
Expression: camelcase('volume_3d')
Reported output: volume3D
Where that came from: The `How to reproduce` block: `console.log(camelcase('volume_3d')); // volume3D`. The console.log wrapper is not part of the call.

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('volume_3d')` still produces volume3D (read volume3D)

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('volume_3d')` still produces volume3D (read volume3D)
right-failure	pass	Reproduced the reported failure: camelcase('volume_3d') and camelcase('volume3d') both return 'volume3D'.
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.

bench external · checks · RECORDED5 checks

The RECORDED 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	failure: 'xo' is not recognized as an internal or external command
right-failure	fail	Expected `camelcase('volume_3d')` still producing volume3D.
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.

captured failure signatureRECORDED · normalized

failure: 'xo' is not recognized as an internal or external command

Fell back to `npm test`, which failed with "'xo' is not recognized as an internal or external command" — the devDependency binary was not resolvable in the execution plane.

Provider heuristic, sandbox local. bench/external/README.md, the Results table and "The top three failure modes". Run 2026-08-21. Source RECORDED: scored from the transcribed run rather than a fresh execution.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 20591fb, 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 20591fbda80c5c15e446766e877530f00ec1c5d1
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