It's worth noting that in the .NET world, there is a useful extension point provided by Roslyn compiler that can be used for shipping analyzers and codefixes using the standard packaging tools (NuGet). Static analysis distributed in such way is automatically integrated into both IDE and CI workflows -- as its directly supported by compilers.
This means that you can static analysis checks besides your library. For example, you have unit testing library that expects to be used in a certain way that cannot be completely described using type system -- it expects that test methods marked by some test attribute has to be public. Such library can include analyzer that would check usages of types from the library and report warnings. User of the library don't have to do a thing to register such analyzer, it will just work.
This means that you can static analysis checks besides your library. For example, you have unit testing library that expects to be used in a certain way that cannot be completely described using type system -- it expects that test methods marked by some test attribute has to be public. Such library can include analyzer that would check usages of types from the library and report warnings. User of the library don't have to do a thing to register such analyzer, it will just work.