JitPack is a novel package repository for JVM and Android projects. It builds Git projects on demand and provides you with ready-to-use artifacts (jar, aar).

If you want your library to be available to the world, there is no need to go through project build and upload steps. All you need to do is push your project to GitHub and JitPack will take care of the rest. That’s really it! Need help setting up a repo? Come to Gitter

In case your project is already on GitHub, JitPack makes sure it can be built by anyone. Want to use a GitHub library in your project? Follow the simple steps explained in the ‘Building with Jitpack’ section.

For issues and enhancements, please use the JitPack GitHub repository. The repository contains this documentation and contributions are welcome there as well.

Building with JitPack

If you are using Gradle to get a GitHub project into your build, you will need to:

Step 1. Add the JitPack maven repository to the list of repositories:

    url "https://jitpack.io"

Step 2. Add the dependency information:

That’s it! The first time you request a project JitPack checks out the code, builds it and sends the Jar files back to you.

To see an example head to jitpack.io and ‘Look Up’ a GitHub repository by url.

Gradle example:

    allprojects {
        repositories {
            maven { url "https://jitpack.io" }
   dependencies {
        compile 'com.github.User:Repo:Version'

Note: when using multiple repositories in build.gradle it is recommended to add JitPack at the end. Gradle will go through all repositories in order until it finds a dependency.


Snapshot versions are useful during development. A snapshot is a version that has not been released. The difference between a real version and a snapshot is that snapshot might still get updates. Snapshot versions are useful during development process and JitPack provides two ways to get them. You can specify a version for your dependency as:

For example:

    // dependency on the latest commit in the master branch
    compile 'com.github.jitpack:gradle-simple:master-SNAPSHOT'

Adding -SNAPSHOT will build the latest commit on the master branch.

Gradle can cache the SNAPSHOT builds. You could add the following configuration in your build.gradle file in order to ensure Gradle always picks up the ‘freshest’ version of the build:

configurations.all {
    resolutionStrategy.cacheChangingModulesFor 0, 'seconds'

Or you could also run Gradle from the command line with the --refresh-dependencies flag. See the Gradle documentation for more information on how to configure caching for changing dependencies.

Note If using Android Studio, don’t forget to press File->Synchronize after updating to a newer snapshot.

Also see the Guide to building for more details and instructions on building multi-module projects.

If the project doesn’t have any GitHub Releases, you can get the latest snapshot build. In this case, use the short commit id as the version. You can also place tags on other branches and then build using those tags.

Tip: You can also automate GitHub releases with Gradle release & version management plugin

Publishing on JitPack

Publishing your library on JitPack is very simple:

As long as there’s a build file in your repository and it can install your library in the local Maven repository, it is sufficient for JitPack. See the Guide to building on how to publish JVM libraries and Guide to Android on how to publish Android libraries.

Tip: You can try out your code before a release by using the commit hash as the version.

Some extras to consider

Add dependency information in your README. Tell the world where to get your library:

   repositories {
        maven { url "https://jitpack.io" }
   dependencies {
         compile 'com.github.jitpack:gradle-simple:1.0'



Other Git hosts

JitPack also works with other Git hosting providers. The only difference is the groupId of your artifacts:

To see an example, head to https://jitpack.io and ‘Look Up’ a Git repository by url.

Custom domain name

If you want to use your own domain name as the groupId instead of com.github.yourcompany, you can. We support mapping your domain name to your GitHub organization. Then, instead of ‘com.github.yourcompany’ groupId, you can use ‘com.yourcompany’ while the name of the project and version remains the same.

To enable your own domain name:

  1. Add a DNS TXT record that maps git.yourcompany.com to https://github.com/yourcompany. This needs to be configured at your domain name provider such as GoDaddy. For example see How to add a TXT record.

  2. Go to https://jitpack.io/#com.yourcompany/yourrepo and click Look up. If DNS resolution worked then you should see a list of versions.

  3. Select the version you want and click ‘Get it’ to see Maven/Gradle instructions.

Example: https://jitpack.io/#io.jitpack/gradle-simple

To check that the DNS TXT record was added, run the command dig txt git.yourcompany.com. For example:

~$ dig txt git.jitpack.io
git.jitpack.io.     600 IN  TXT "https://github.com/jitpack"


Add this line to your README.md to show a status badge with the latest release:



If you are using a custom domain or BitBucket, use:



Or, if you prefer the flat-squared style:




See the FAQ page