1. The project has a dependency on MongoDB, but does not say so in the readme, specify how to set one up or a link on how to do that.
2. The project has a dependency on .env but does not specify an example config or how to set one up and where it should be located. I think preferring a structured and lintable file like yaml or toml makes it easy to avoid petty issues.
3. server.ts:19 the http server is started even if a connection to mongo fails even though mongo is a direct dependency of the server. You can prevent this by using onconnect.
4. src/controller/userController.ts:18 even though you are await a promise, it is not wrapped inn a try catch which can lead to unpredictable behaviours when the mongo server fails.
5. Prefer using named status codes rather than just the code, since a named one is self documenting. er. HttpStatus.BadRequest over 400
6. src/controller/userController.ts:29 sending unsanitized objects from the db can cause a leakage of critical resources like hashed passwords.
7. src/db/mongo.ts:10 you are not logging the actualy error which will make debugging painful
8. src/middleware/auth.ts:6, you need to evaluate the legnth on an array before you select an index, otherwise this can crash you application. People can exploit it to DDoS you server.
9. src/middleware/auth.ts:12 the evaluation of a jwt token on startup or in post application startup is something you want to do to prevent people from forgetting and having a predetermined key used for encryption.
10. src/models/userModels.ts:34-36 too much redundancy.
11. src/validators/createUserValidators.ts:9 you might have a bug here.

Other ancillary Points

1. add a linter for the whole project
2. Prefer organize you files around a module rather than functionality. Functionality will alsways change depending on business need. Modules more or less remain, plus models are easier to reason about. A sample orgainition might looke like this

user/model.ts
user/controller.ts
user/validator.ts
user/routes.ts

3. Have tests close to files. this way it is easy to perceive which files are missing tests and it is easy to add them on. Having a convention around tests also helps. eg. test for user/controller.ts goes in user/controller_test.ts and you can have jest test all files that have _tests.ts at the end of file names.