Sign in

Evidencedecamelize-21

Decamelizing a capitalized word gives odd results

decamelize#21, at commit 9ac3cb5. 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
102.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/decamelize
Issue
#21
Pinned commit
9ac3cb535f46e08eedb6ac7417e9bc26f5ff58bf

01The signal

The report, exactly as it was filed.

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

decamelize#21 · as filedcommit 9ac3cb5

Decamelizing a capitalized word gives odd results

Hello,

When decamelizing an upcase word one gets odd results like this:

```js
decamelize('ADDRESS1') === 'addres_s1'
```

Not sure what the logic is in it but I would expect that it returns `address1`

Regards
Issue
#21
Commit
9ac3cb535f46e08eedb6ac7417e9bc26f5ff58bf
Why this commit
The first parent of the fix commit 26c7530b4fe5674809cb91c3df2615cf065492ab, 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
decamelize('ADDRESS1') produces 'addres_s1'; the fix makes it produce 'address1'.
Expression
decamelize('ADDRESS1')
Reported output
'addres_s1'
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: `decamelize('ADDRESS1') //=> 'addres_s1'`. The report sat in the CODE_NO_ANNOTATION_AT_ALL 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
`decamelize('ADDRESS1')` still produces 'addres_s1' (read addres_s1)
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`decamelize('ADDRESS1')` still produces 'addres_s1' (read addres_s1)
right-failurepassReproduced the reported failure: decamelize('ADDRESS1') produces 'addres_s1'; the fix makes it produce 'address1'.
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 9ac3cb5, 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/decamelize
git checkout 9ac3cb535f46e08eedb6ac7417e9bc26f5ff58bf
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