#Fortify bug for golang.org/x/tools
16 messages · Page 1 of 1 (latest)
Yes
My application never use any jquery related stuffs .. this is a headache...I have been facing this for so long
it looks like it’s in golang.org/x/tools/cmd/present, which is a runnable program and not something that gets built into your program including the module
your options are, then, roughly:
- report the vulnerability and hope it gets fixed, but the fact that it’s so old and likely abandoned means it’s probably not high priority to fix (it might be updating to the program to support an entirely new major version, not just dropping a new version in)
- understand that the tool is reporting something not immediately concerning, and move on
- stop using golang.org/x/tools
there’s no magic bullet here, those really are your options
Is there any replacement for this package? It breaks code if I don't use this package
How can I remove it from my code
it might take some major surgery, yes
the tool being stupid to report stuff not in use is the main issue. but you could always fork x/tools and remove everything you don’t use from your fork
How can it be done?
you could also go vendor and remove the present/ dir
Go mod vendor directory has no such file ...I have searched that
if you’re paying for whatever fortify is, I’d report a bug to them.
and if the vendor dir doesn’t have it shouldn’t the problem be solved? (or again google “how to make a fork of a go module”)
