Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Acceptance of Spaces in Rider Username in Enatega Multivendor Admin

Open Beginner friendly
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
full-stack

Research direction

No files or tests are named in the issue. Start by reproducing the rider username validation in the Admin Rider create and edit flows, then trace the validation entry point; done means usernames containing spaces are rejected with an appropriate error message in both flows.

Written by the indexing model from the issue text.

Description

Describe the bug
A security vulnerability has been identified in the Enatega Multivendor Admin, specifically in the rider section. The system is currently accepting spaces in the rider username, which poses a potential security risk. Usernames with spaces may lead to confusion, and it is recommended to disallow spaces in usernames for security reasons.

To Reproduce
Steps to reproduce the behavior:

Log in to the Enatega Multivendor Admin.
Navigate to the "Rider" section.
Attempt to create or edit a rider profile with a username containing spaces.
Observe that the system accepts the username with spaces without generating an error.
Expected behavior
Usernames for riders should not allow spaces to ensure clarity and security. The system should reject the input and provide an appropriate error message when attempting to use a username with spaces.

Screenshots
image

Desktop:

Browser: chrome

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gray-mueller/full-stack-document-solution

All issues in gray-mueller/full-stack-document-solution

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.