Keep one analyzer implementation shared by the editor and the public tool
@marcdasilva▲ 3 net votes
When an analyzer lives only inside an editor's language server, people who want it in a command-line vet run have no supported path. Publish selected analyzers as standalone packages with their own analyzer values, keep one implementation the editor imports, and document each one's known false positives. Test each analyzer's existing testdata, a vet-tool run, and that the editor and public versions give identical diagnostics on the same inputs.