Veracode maintains an official Jenkins plugin that we publish via our Help Center and will shortly be publishing to the marketplace (within the next few months). Today we get a lot of confused users asking for assistance on the open source veracode-scanner plugin via our support channels, and I note you have the opposite problem here.

We'd like some help in reducing the confusion around which version of the plugin is supported by Veracode. I appreciate that the plugin listing page now says "not supported by Veracode" in big red letters but unfortunately this hasn't solved the problem. Is it possible to get the veracode-scanner plugin renamed? Or do you have any other creative ideas about how we might address the problem?

Thanks for the work you've done on the plugin to date; I'm hopeful we can find a solution to this ongoing confusion.