Aurimas Liutikas 
A post about how a library could be considered complete, might not need any further changes, and all of that is totally OK!
Audrius@Aurimas everything looks simple and fit nicely into categories in theory.
Then real life hits. Does library need Kotlin compiler plugin, or another subdependency with kt compiler plugin like compose, or gradle plugin that depends on AGP, or depends on NDK, or has custom lints, or needs IDE plugin, or packaging includes all fancy stuff like gradle metadata for multiplatform compatibility. Abandoned library is liability. If that is not math library with 0 dependencies than it's not guaranteed that it will be compatible with latest tools in the project.
Then real life hits. Does library need Kotlin compiler plugin, or another subdependency with kt compiler plugin like compose, or gradle plugin that depends on AGP, or depends on NDK, or has custom lints, or needs IDE plugin, or packaging includes all fancy stuff like gradle metadata for multiplatform compatibility. Abandoned library is liability. If that is not math library with 0 dependencies than it's not guaranteed that it will be compatible with latest tools in the project.