HR generally doesn't have the training to distinguish good code from bad code, and will be counting your repos or the lines of code in your repos if they look at your github at all.
Ultimately, the bigger issue is whether or not you feel like your competence should disqualify you from a position. If you feel that way, then you should do something about it before applying for jobs. A good way to improve your skills is to fix the code you've already written, and doing that in a public repo demonstrates progress in a way that technical peers can appreciate.
(Re: trendy frameworks -- fashion has nothing to do with fit, and trendy frameworks are overhyped specifically because people use them when they are inappropriate for the task at hand. It's not hard to pick up a new framework on the job if you're asked to do so; I would avoid trendy frameworks and focus on the basics until somebody who controls your paycheck tells you otherwise. After all, which framework is currently trendy is liable to change inbetween getting a job and being able to start work, and the people making decisions about which frameworks will be used are almost inevitably tied to the trend cycle but ten or fifteen years behind it.)