Evidencemoment-1075

Problem with parsing Unixtime format

moment#1075, at commit e69c63e. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome: REPRODUCED_NOT_DIAGNOSED
Wall time: 108.8s
Checks: 5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome: not recorded
Checks: none run

Repository: moment/moment
Issue: #1075
Pinned commit: e69c63ec1b7c9afae7440030258deb4efb0b446b

01The signal

The report, exactly as it was filed.

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

moment#1075 · as filedcommit e69c63e

Problem with parsing Unixtime format

This problem is:

```
moment('1371065286', ['X']).isValid()
false
```

Repository: moment/moment
Issue: #1075
Commit: e69c63ec1b7c9afae7440030258deb4efb0b446b
Why this commit: The first parent of the fix commit 9c6e4468fdc9e33300d68b687c019c56c22f6035, which GitHub binds to this issue via CROSS_REFERENCED_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: moment('1371065286', ['X']).isValid() produces false; the fix makes it produce true.
Expression: moment('1371065286', ['X']).isValid()
Reported output: false
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: `moment('1371065286', ['X']).isValid() //=> false`. 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

`moment('1371065286', ['X']).isValid()` still produces false (read false)

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	`moment('1371065286', ['X']).isValid()` still produces false (read false)
right-failure	pass	Reproduced the reported failure: moment('1371065286', ['X']).isValid() produces false; the fix makes it produce true.
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 e69c63e, 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/moment/moment
git checkout e69c63ec1b7c9afae7440030258deb4efb0b446b
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