Evidenceobject-inspect-6

Printing of primitive wrapper objects

object-inspect#6, at commit 559ae4c. 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: 120.1s
Checks: 5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome: not recorded
Checks: none run

Repository: inspect-js/object-inspect
Issue: #6
Pinned commit: 559ae4cf0785152a1296fef6cf49f4ad8572b6bf

01The signal

The report, exactly as it was filed.

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

object-inspect#6 · as filedcommit 559ae4c

Printing of primitive wrapper objects

`new String()`, etc. should be handled specially. Current behavior:

```
> var oi = require('object-inspect');
undefined
> oi(new Number(5))
'{}'
> oi(new String('hello'))
'{ 0: \'h\', 1: \'e\', 2: \'l\', 3: \'l\', 4: \'o\' }'
> oi(new Boolean(true))
'{}'
```

 cc @ljharb

Repository: inspect-js/object-inspect
Issue: #6
Commit: 559ae4cf0785152a1296fef6cf49f4ad8572b6bf
Why this commit: The first parent of the fix commit 0fbf348d1888408fae36cace8abfe43295922e72, 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: oi(new Number(5)) produces '{}'; the fix makes it produce 'Object(5)'.
Expression: oi(new Number(5))
Reported output: '{}'
Where that came from: Read mechanically from the report's fenced code, REPL form: `> oi(new Number(5)) '{}'`.

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

`oi(new Number(5))` 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	`oi(new Number(5))` still produces '{}' (read {})
right-failure	pass	Reproduced the reported failure: oi(new Number(5)) produces '{}'; the fix makes it produce 'Object(5)'.
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 559ae4c, 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/inspect-js/object-inspect
git checkout 559ae4cf0785152a1296fef6cf49f4ad8572b6bf
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