Evidencemustache-330

Integer value 0 gets rendered as "[object Object]"

mustache.js#330, at commit 48fb97b. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
ERRORED
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
Issue
#330
Pinned commit
48fb97b4efae2da79342c10570af3d202a16f673

01The signal

The report, exactly as it was filed.

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

mustache.js#330 · as filedcommit 48fb97b

Integer value 0 gets rendered as "[object Object]"

Test code:

```
Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]});
```

Expected result:

```
"0, 1, 2, "
```

Actual result:

```
"[object Object], 1, 2, "
```
Issue
#330
Commit
48fb97b4efae2da79342c10570af3d202a16f673
Why this commit
The first parent of the fix commit 411edae06129af7816e37cd7904869e6e45618d2, 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
Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]}) produces '[object Object], 1, 2, '; the fix makes it produce '0, 1, 2, '.
Expression
Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]})
Reported output
"[object Object], 1, 2, "
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: `Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]}) //=> "[object Object], 1, 2, "`. 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
`Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]})` still produces "[object Object], 1, 2, " (read [object Object], 1, 2, )
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.
CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]})` still produces "[object Object], 1, 2, " (read [object Object], 1, 2, )
right-failurepassReproduced the reported failure: Mustache.render("{{#nums}}{{.}}, {{/nums}}", {nums: [0, 1, 2]}) produces '[object Object], 1, 2, '; the fix makes it produce '0, 1, 2, '.
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 48fb97b, 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/janl/mustache.js
git checkout 48fb97b4efae2da79342c10570af3d202a16f673
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color