Eddy has a valid point here.
But renaming a vulnerable jQuery library that qualifies for retirement to escape a vulnerable code version detection is known as "security by obscurity" and in that way you are putting your users/visitors at risk. Seems you take that into the bargain, when you wanna cheat, just cheat. Normal procedure is to retire the vulnerable code library, zip file it for later reference and then mitigate the code to a later version that does not come flagged. Any other procedure is not considered "best practices", just like altering excessive server header info with something else is not. Software should not speak out period.
polonus