Sign in

Evidencemoment-323

utc(Number) not working

moment#323, at commit 6ed1808. 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
98.9s
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
#323
Pinned commit
6ed18086f0a466ccab719e67c4ad3cf70877d6bb

01The signal

The report, exactly as it was filed.

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

moment#323 · as filedcommit 6ed1808

utc(Number) not working

<h3>Example</h3>

<code>moment.utc(1338499506000);</code>

<h3>Result</h3>

<code>{ _d: Invalid Date, _isUTC: true }</code>
Repository
moment/moment
Issue
#323
Commit
6ed18086f0a466ccab719e67c4ad3cf70877d6bb
Why this commit
The first parent of the fix commit 635bd20e91cdda3068432e44cfde818d55ece099, which GitHub binds to this issue via REFERENCED_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
moment.utc(1338499506000) produces { _d: Invalid Date, _isUTC: true }; the fix makes it produce { _d: 2012-05-31T21:25:06.000Z, _isUTC: true }.
Expression
moment.utc(1338499506000)
Reported output
{ _d: Invalid Date, _isUTC: 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: `moment.utc(1338499506000) //=> { _d: Invalid Date, _isUTC: true }`. The report sat in the NO_FENCE_PROSE_ONLY 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.utc(1338499506000)` still produces { _d: Invalid Date, _isUTC: true } (read { _d: Invalid Date, _isUTC: true })
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`moment.utc(1338499506000)` still produces { _d: Invalid Date, _isUTC: true } (read { _d: Invalid Date, _isUTC: true })
right-failurepassReproduced the reported failure: moment.utc(1338499506000) produces { _d: Invalid Date, _isUTC: true }; the fix makes it produce { _d: 2012-05-31T21:25:06.000Z, _isUTC: 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 6ed1808, 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 6ed18086f0a466ccab719e67c4ad3cf70877d6bb
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