From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

That would be the best option imo. To make it even more comfortable you can write a settings plugin (`.settings.gradle(.kts)` extension) that you apply in all `settings.gradle(.kts)` files which uses the newer `dependencyResolutionManagement {}`  to declare the repositories.

For publishing the precompiled script plugins to a repo, you basically only need to add `maven-publish` and configure the repository to publish to. Example / explanation:
<https://github.com/jjohannes/gradle-plugins-howto/commit/publish-plugins#diff-6262d4c69eea52ccb569614180adeb6bdb21dfcda8ace52dbed09ad698f8d0e0>

Pre-compiled settings plugin example that declares a repository:
<https://github.com/jjohannes/understanding-gradle/blob/main/14_Settings_Plugins/my-build-logic/structure-plugins/src/main/kotlin/my-project-structure.settings.gradle.kts#L7-L8|https://github.com/jjohannes/understanding-gradle/blob/main/14_Settings_Plugins/my[…]lugins/src/main/kotlin/my-project-structure.settings.gradle.kts>