Sign in

Evidencevalidator-343

Full-width chars are not valid in an email address

validator.js#343, at commit c89c271. 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
54.2s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
validatorjs/validator.js
Issue
#343
Pinned commit
c89c271b2671d51deb11e2e0f88f0c2cf178fef9

01The signal

The report, exactly as it was filed.

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

validator.js#343 · as filedcommit c89c271

Full-width chars are not valid in an email address

Hi All,

I use validator.js in my app. Recently I found that there ware some email address like `somename@ｇｍａｉｌ.com`. I add this address to the test code, and it shows that this is an valid email.
Issue
#343
Commit
c89c271b2671d51deb11e2e0f88f0c2cf178fef9
Why this commit
The first parent of the fix commit 7384f328a005f30c252559a24717299b279d7376, 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
validator.isEmail('somename@ｇｍａｉｌ.com') produces true; the fix makes it produce false.
Expression
validator.isEmail('somename@ｇｍａｉｌ.com')
Reported output
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: `validator.isEmail('somename@ｇｍａｉｌ.com') //=> true`. The report sat in the NO_FENCE_INLINE_CODE_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

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 `validator.isEmail('somename@ｇｍａｉｌ.com')` still producing 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 c89c271, 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/validatorjs/validator.js
git checkout c89c271b2671d51deb11e2e0f88f0c2cf178fef9
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