You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
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
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:
(mockReputationProfiles is a plain object keyed by exact-case username.)
src/lib/api.ts#fetchReputationByUsername:
constuser=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.
@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().
@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.
@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.
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.
😎 @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.
Activity
Muyideen-js commentedon Aug 24, 2026
@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Muyideen-js to this issue.
OpensrcLord commentedon Aug 24, 2026
@OpensrcLord has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @OpensrcLord to this issue.
OutstandingVick commentedon Aug 24, 2026
@OutstandingVick has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @OutstandingVick to this issue.
madisonsc52-del commentedon Aug 24, 2026
@madisonsc52-del has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @madisonsc52-del to this issue.
Kriss255 commentedon Aug 24, 2026
@Kriss255 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kriss255 to this issue.
thelight08 commentedon Aug 24, 2026
@thelight08 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @thelight08 to this issue.
datboilondon commentedon Aug 24, 2026
@datboilondon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @datboilondon to this issue.
CITYZEN-AL-MUSTAPHA commentedon Aug 24, 2026
@CITYZEN-AL-MUSTAPHA has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @CITYZEN-AL-MUSTAPHA to this issue.
d1a-m3n commentedon Aug 24, 2026
@d1a-m3n has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @d1a-m3n to this issue.
abrahambaba1 commentedon Aug 24, 2026
@abrahambaba1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @abrahambaba1 to this issue.
Priest-Codes commentedon Aug 24, 2026
@Priest-Codes has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Priest-Codes to this issue.
macityhub-bot commentedon Aug 24, 2026
@macityhub-bot has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @macityhub-bot to this issue.
drips-wave commentedon Aug 24, 2026
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 🌊
drips-wave commentedon Aug 25, 2026
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.