Skip to content

Reputation profile lookups are case-sensitive, so a URL with different letter casing than the stored GitHub username 404s even though the profile exists #245

Closed

Description

@chonilius

GitHub usernames are canonically case-insensitive (torvalds and Torvalds resolve to
the same account on github.com), but every lookup in this app's reputation flow is a
strict, case-sensitive equality check:

src/app/reputation/[handle]/page.tsx:

const profile = await fetchReputationByUsername(
  handle,
  mockReputationProfiles[handle] ?? null,
);

(mockReputationProfiles is a plain object keyed by exact-case username.)

src/lib/api.ts#fetchReputationByUsername:

const user = users.find((u) => u.username === username);

(a strict === string comparison, not a case-insensitive one.)

Visiting /reputation/priyaeth resolves correctly, but /reputation/Priyaeth or
/reputation/PRIYAETH — URLs a person might reasonably type, or that another surface in
the app might construct from GitHub's own case-preserving display of the same username —
finds no match in either the mock lookup or the live users.find, and the page calls
notFound(), 404-ing a profile that genuinely exists under a different letter casing.

Suggested fix: normalize handle (and the comparison in fetchReputationByUsername) to
a consistent case — e.g. lowercase both sides of the username === username comparison,
and look up mockReputationProfiles case-insensitively — so the profile page behaves the
way GitHub's own username resolution does.

Activity

  1. added
    bugSomething isn't working
    very hardVery difficult task, expert-level effort required
    help wantedExtra attention is needed
    enhancementNew feature or request
    on Aug 21, 2026
  2. Muyideen-js commented on Aug 24, 2026

    @Muyideen-js

    @Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I'd like to work on this issue by normalizing the handle in the reputation page and updating fetchReputationByUsername to compare usernames case-insensitively, ensuring both mock and live lookups resolve profiles regardless of letter casing. I'll add a test covering a mixed-case URL like /reputation/Priyaeth to verify it no longer triggers notFound().

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Muyideen-js to this issue.

  3. OpensrcLord commented on Aug 24, 2026

    @OpensrcLord

    @OpensrcLord has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello @maintainer, I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @OpensrcLord to this issue.

  4. OutstandingVick commented on Aug 24, 2026

    @OutstandingVick

    @OutstandingVick has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi! I’d love to contribute to MergeFi and take ownership of this reputation lookup fix.

    I’ll normalize GitHub handles across both the route and API lookup paths so reputation profiles resolve case-insensitively, including mock data, and add focused regression coverage for mixed-case URLs to prevent valid profiles from incorrectly 404ing.

    I’m excited to contribute and collaborate with the team. Please assign this issue to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @OutstandingVick to this issue.

  5. madisonsc52-del commented on Aug 24, 2026

    @madisonsc52-del

    @madisonsc52-del has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi maintainer i can work on this, I'll make sure to work on the issue asap

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @madisonsc52-del to this issue.

  6. Kriss255 commented on Aug 24, 2026

    @Kriss255

    @Kriss255 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello Maintainer, I’d be happy to take ownership of this issue and deliver a quality pull request once completed.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kriss255 to this issue.

  7. thelight08 commented on Aug 24, 2026

    @thelight08

    @thelight08 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Interested in contributing to this issue. I'll ensure the implementation is clean, tested, and follows project conventions.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @thelight08 to this issue.

  8. datboilondon commented on Aug 24, 2026

    @datboilondon

    @datboilondon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    i would love for this issues to be assigned to me thank you

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @datboilondon to this issue.

  9. CITYZEN-AL-MUSTAPHA commented on Aug 24, 2026

    @CITYZEN-AL-MUSTAPHA

    @CITYZEN-AL-MUSTAPHA has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I'd like to be assigned to this issue. I'll deliver a clean, maintainable solution that matches the requirements.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @CITYZEN-AL-MUSTAPHA to this issue.

  10. d1a-m3n commented on Aug 24, 2026

    @d1a-m3n

    @d1a-m3n has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I’d like to work on this issue to fix case-sensitive profile lookups. I’ll normalize username comparisons and test different casing variations to ensure profiles resolve correctly.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @d1a-m3n to this issue.

  11. abrahambaba1 commented on Aug 24, 2026

    @abrahambaba1

    @abrahambaba1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    hi, I'd love to contribute to this , please assign this issue to me

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @abrahambaba1 to this issue.

  12. Priest-Codes commented on Aug 24, 2026

    @Priest-Codes

    @Priest-Codes has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    ​Hi maintainer, I would love to work on this issue. I can get started on it right away. Could you please assign it to me

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Priest-Codes to this issue.

  13. macityhub-bot commented on Aug 24, 2026

    @macityhub-bot

    @macityhub-bot has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi Maintainer, I’m on this one. I’ll dig into it and circle back with an update shortly.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @macityhub-bot to this issue.

  14. drips-wave commented on Aug 24, 2026

    @drips-wave

    Congratulations, @presidoclintonbased-alt! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @presidoclintonbased-alt: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  15. drips-wave commented on Aug 25, 2026

    @drips-wave

    This issue has been completed by @presidoclintonbased-alt as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @presidoclintonbased-alt: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programbugSomething isn't workingenhancementNew feature or requesthelp wantedExtra attention is neededvery hardVery difficult task, expert-level effort required

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions