It may, or may not, rattle you, but most tech leads that are forced, by the company's pipeline, to take part in the recruitment pipeline don't really care about you OSS projects.
I know I didn't when I was tasked with such chore.
Yes, companies like saying OSS contributions are an advantage and "We look forward to what you are about to share with us", and I guess HR goes ga-ga over such entries (even if all the repo has is a readme), but, look at it from the TL perspective: s/he has their own tasks to clear at work, on top of that, now they have to squeeze in interviewing and grading the candidates', plural, take-home tech challenges and prioritize which one to call for an on-site... do they really care, like really care about your OSS repos, old or new?
What do you think?
Only, o-n-l-y, time I took a look at a candidate's GitHub profile was when I didn't like his coding, but I saw the guys has some chops and figured maybe it was just time constraint ont the take-home task, he has a day-time job as well, so maybe that coding, while showing promise, is just stress and exhaustion combined.
Candidate had about 3-4 projects in his repo total, not one of them even with 1 star, and all abondaned at some stage or another.
You can guess what I decided about him, but the point is, that was the one and only time I felt the need to burden myself with looking at a candidate's OSS efforts.
To finish my reply off, I would say, like the rest of the answers here, that as long as that project is old, and you feel, and can prove by demonstration, that you have grown as a developer from that time, and hey, 100 stars is no small feat either, in such a grand "universe" as GitHub... keep the repo and be proud of it!
Those are the things you cut your teeth on, trying out new tech, and you grew because of it.
That is your coding legacy.
Do you think is ashamed of his/her rookie years? Or are they proud to reminisce upon them, thinking "Wow, did I come a looong way from then"?