Sign in

Evidencecamelcase-keys-13

Weird behaviour with array of objects as input

camelcase-keys#13, at commit 983678a. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
INCONCLUSIVE
Wall time
66.4s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
sindresorhus/camelcase-keys
Issue
#13
Pinned commit
983678a5a4f2aac93987159e53fd7b6d205969b9

01The signal

The report, exactly as it was filed.

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

camelcase-keys#13 · as filedcommit 983678a

Weird behaviour with array of objects as input

```
camelcaseKeys([{'foo-bar': true}], {deep:true})
```
gives
```
{
    0: {
        fooBar: true
    }
}
```
I was expecting 
```
[
    {
        fooBar: true
    }
]
```
Since
```
camelcaseKeys({'test': [{'foo-bar': [{'foo-baz': true}]}]}, {deep:true});
```
Gives
```
{
    test: [
        {
            fooBar: [{ fooBaz }]
        }
    ]
}
```
Issue
#13
Commit
983678a5a4f2aac93987159e53fd7b6d205969b9
Why this commit
The first parent of the fix commit 13ae924f419f473597a70035b834745842ea0180, 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
camelcaseKeys([{'foo-bar': true}], {deep:true}) does not produce [{"fooBar": true}]; the fix makes it do so.
Expression
camelcaseKeys([{'foo-bar': true}], {deep:true})
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: `camelcaseKeys([{'foo-bar': true}], {deep:true}) //=> [{"fooBar": true}]`. 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

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

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-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `camelcaseKeys([{'foo-bar': true}], {deep:true})` not producing [{"fooBar": true}].
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 983678a, 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-keys
git checkout 983678a5a4f2aac93987159e53fd7b6d205969b9
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