test(crypto): cover uppercase hex in timingSafeEqualHex

[kiannidev]

Summary

• Add regression coverage that timingSafeEqualHex treats uppercase and lowercase hex as equal.

No-issue rationale

Test-only coverage lock with no linked issue.

Test plan

• npx vitest run test/unit/crypto.test.ts

Made with Cursor

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.73%. Comparing base (8b0ac26) to head (ddea952).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2111   +/-   ##
=======================================
  Coverage   95.73%   95.73%           
=======================================
  Files         223      223           
  Lines       24741    24741           
  Branches     8969     8969           
=======================================
  Hits        23685    23685           
  Misses        433      433           
  Partials      623      623           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JSONbored]

Moving forward, please do not open more than 2 PRs at a time - i'll be adding a configuration to gittensory orb to auto-close PRs over that threshold.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-01 17:11:26 UTC}

1 file · 1 AI reviewer · no blockers · readiness 55/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
The diff is a narrow test-only change that adds coverage for `timingSafeEqualHex("ABCD", "abcd")`, confirming mixed-case hex strings compare equal. That matches the intended API behavior for hex decoding and does not change production behavior. The only notable issue is that the existing test name now undersells the valid-case assertions it contains.

Nits — 3 non-blocking

• nit: `test/unit/crypto.test.ts:24` names the case `rejects invalid hex operands`, but the body now also covers valid equal, unequal, and uppercase-normalization behavior.
• Rename or split `test/unit/crypto.test.ts:24` so the uppercase regression sits under a positive-case description such as `compares valid hex operands in constant time`.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (size label size:XS; no linked issue context).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 2694 registered-repo PR(s), 1487 merged, 48 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kiannidev; Gittensor profile; 2694 PR(s), 48 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: kiannidev
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: TypeScript, C++, HTML, MDX, Rust
• Official Gittensor activity: 2694 PR(s), 48 issue(s).
• Related work: Items reference the same linked issue feat(enrichment): render section + analyzerStatus wiring test for new local analyzers #2037. (issue #2037, PR #2395)
• Related work: Open PR work references issue feat(enrichment): render section + analyzerStatus wiring test for new local analyzers #2037. (issue #2037, PR #2395)
• Related work: Titles/paths share 6 meaningful terms. (PR #2374, PR #2376)

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Triage stale or unlinked PRs.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review