Read the article
Start from what an interviewer is actually trying to learn. A fresher's project is evidence of what you can do. The interviewer is not hoping to catch you out. They want to know if you understand the thing well enough that they can trust the rest of your resume. A project that is half borrowed and fully understood passes that test. A project claimed as entirely original, and not understood, does not.
That is why honesty is the stronger position, and also the easier one. If you have told the truth, you do not have to remember which parts you claimed. You only have to know the project.
So make a list before the interview. Go through the project and mark each part: written by me, adapted from something, suggested by someone, produced with a tool, or written by a teammate. Most students are surprised by how much falls in the middle. That is fine. The list is for you.
Then choose a plain way to say each one. 'I started from the documentation example and changed it to fit our data.' 'My senior suggested this approach, and I tried two others before agreeing.' 'I used an online tool to get a first version of this function, then I tested it with these cases and fixed these two problems.' Each of these says what the help was, and what you did next. The interviewer's follow-up will be about your part, which is where you can talk with confidence.
Avoid the extremes. 'I built everything myself' is a risky sentence, because the second question will test it. 'I just copied it' is also not helpful, and usually not true. Most students did real work on top of what they borrowed. Say what that work was.
Next, test your understanding, because this is where help becomes a problem. Anything on your resume, you should be able to explain. Close the code and describe one module aloud. Change one small behaviour without looking anything up. Explain a bug and how you would find it. Name each library you used and say what it does for the project. Where you cannot do these things, that is the part to study, and it is better to find out now.
A word on rules. Colleges have their own policies about the use of outside help and online tools in academic work, and those are separate from what an employer asks. Follow your college's rules for submissions. For interviews, the advice above holds: say what happened and show that you understand it. If you are unsure what your college permits, ask your guide before you submit, not after.
And if you are asked something you cannot answer, say so. 'I do not remember why we chose that, but I would look at the options and compare them like this.' Interviewers hear a lot of confident guesses. A clear 'I do not know, and here is how I would find out' tends to be remembered well.