Introducing jbanghub

1 minute read

Today we are introducing JBangHub!


JBang always allowed everyone easily make their own java/kotlin/groovy/etc. command line tools available in a jbang catalog. All it takes is that you make a jbang-catalog in your project, organization or website.

This is what makes things like jbang jreleaser@jreleaser and jbang minecraft-server@microsoft possible with minimal effort.

These can then be called as-is or even installed using jbang app install making them available in your PATH directly.

Many already added lots of catalogs and they are visible on the JBang AppStore, readily available to be used from anywhere with JBang available.

This is anywhere you can run java including from javascript and python - yes, even Jupyter Notebooks can access Java with JBang.

To make it even easier and make it possible for anyone to make their favourite tools available under a nice and simple name we are introducing JBangHub, a GitHub organization where we invite everyone to contribute scripts and tools they would like to see easily available.

JBangHub is there to let anyone help any project become more easily accessible to the Java community.

Automatic dependency updates

We made a jbang-catalog template available that setups of a jbang-catalog with automatic renovate bot based updates.

All repos in JBangHub uses this to ensure any Maven referenced artifacts will get updates, but anyone can use this in their own jbang-catalog outside JBangHub too.

Just start it using jbang init -t jbang-catalog <reponame> and add aliases to your jbang-catalog.

Default Catalog

The latest release (0.116) of JBang adds jbanghub as a default jbang catalog so when you do jbang catalog list you get something like:


This list is not intended to be every jbang-catalog on the planet - but more a teaser on what is available out there. We encourage and accept edits/updates to that list at

Help expand

Think something is missing - come contribute your favourite tool at JBangHub.

Have fun!




Leave a comment