RipMe: a single jar whose tag carries the release, the commit count and the SHA
Downloads albums from the web in bulk for archive purposes
At a glance
- What is it?
- RipMe is a Java album downloader that runs as one jar on your own machine and needs Java 21 or later. Its version numbers embed four things at once, its maintainer table lists one person twice, the readme has two sections with the same heading, and two of its listed sites are marked broken in the readme itself.
- Who is it for?
- RipMe suits someone archiving public image albums who wants the downloader on their own machine rather than a hosted service, and who is willing to deal with a tool that breaks when a site changes. Check the tag before you trust a build, since the version string tells you the commit count and the SHA, which is more than most jars give you.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 91 days ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- RipMeApp/ripme4,147 ★ · +23
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| RipMeApp/ripme | 4.1k | 4.1k |
23 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The version string carries four pieces of information at once
The readme explains its own naming scheme with an example filename: `ripme-1.7.94-17-2167aa34-feature_auto_release.jar`.
Four parts. The first is a release number, `1.7.94`, given by a person. The second is the number of commits since that version, `17`. The third is a commit SHA, `2167aa34`, which uniquely references the source the jar was built from. The fourth is the branch name, present only when the build is not from main, here `feature/auto-release`.
The readme says this follows the Semantic Versioning specification and uses the format's ability to carry extra data after the hyphen, so that every commit on every branch has its own distinct semver version.
That last sentence contains a typo, distinct spelled with an extra letter, which is a small sign of how long this paragraph has been in the file.
The release tags follow the same scheme. The three most recent are `latest-main` for a development build of main on 15 August 2026, `2.1.21-17-0d8fc72f` on 9 August 2026, and `2.1.20-14-5a3070e4` on 20 September 2025.
Java 21 is a platform decision, not a language preference
The minimum requirement is Java 21 or later, and the readme justifies it in one sentence with a reason that is about platforms rather than features.
It says Java 21 is the most modern possible Java version that allows the project to support the most platforms, and that it is the default JDK on current Debian stable.
So the floor is set by what can still be packaged for the widest set of operating systems. Moving to a newer Java would buy language features and cost installations on older distributions. The readme links a pull request thread and issue 2055 as the discussion behind that choice.
The distribution story is a single file. You download `ripme.jar` from the latest release and the wiki page on running the jar covers the rest, because there is no installer. On macOS there is a Homebrew cask, and the install line is one command that does two things:
brew install --cask ripme && xattr -d com.apple.quarantine /Applications/ripme.jarThe second half removes the quarantine attribute macOS puts on downloaded files, which is why the cask does not need a signed build to be usable.
The readme has two sections with the same heading
There is a maintainers section near the top, listing six people with an activity indicator given as a coloured circle, and a year range for each period of activity.
Then, further down, after the list of supported sites, there is a second section with the same heading, and this one is about compiling and building with Gradle.
Two sections called Maintainers, about different things, in one file.
The first table has its own problem. One person appears twice, listed once for 2016 to 2017 and again for 2025 to present. Either the earlier stint was not merged with the later one, or the same handle genuinely held the role twice and the entry was never consolidated.
The indicators are worth reading as a maintenance signal rather than a decoration. Two entries carry the current indicator and the rest carry the inactive one, including the original creator's 2014 to 2016 entry. So the project has two people currently active and a history of more.
Development moved to a second repository and came back, with stale issues left behind
There is a section on recent development updates that describes a migration rather than a feature.
It states that the current active repository for RipMe is `ripmeapp/ripme`. Then it says that for a while that repository was inactive and development continued at `ripmeapp2/ripme`. Then that maintainers have been updated and development has rejoined the first repository where it will continue.
The fourth line is the one to note: you may find a number of stale issues on either repository until everything is merged back together and statuses are updated.
So the project is telling you its issue tracker contains known noise. Combined with the request to search existing issues before opening a new one, the practical instruction is to expect duplicates and closed-by-accident entries while the merge completes.
The invitation to become a maintainer is routed to a Gitter lobby rather than to the issue tracker, and the same lobby with a Reddit community is listed as the contact.
Two of the listed sites are marked broken in the readme itself
The supported sites list is a bulleted list of sixteen names followed by a link to the full list in the wiki. Two entries carry a parenthetical note.
Twitter is listed as currently broken, needing to be updated for X. DeviantArt is listed as currently broken by major changes to the site.
The readme explains the general condition before the list: websites change over time and therefore rippers, which fundamentally depend on website layouts, can break at any time.
That is a structural property of the project rather than a bug list. Each site adapter parses a page layout, and when the site redesigns, the adapter stops matching. Two broken out of sixteen listed is a reasonable rate for that kind of tool and it is disclosed in the same list as the working ones.
Adding your own adapter is supported by a wiki guide for creating a ripper for HTML websites, and requests for new sites are collected as comments on a single pinned issue rather than as separate issues.
Re-ripping is the feature, and skipping downloaded files is the default
The features list is short, and the second entry is the one that distinguishes this from a download script.
It can easily re-rip albums to fetch new content. So the unit of work is the album, not the file, and running it a second time is a normal operation rather than an error recovery path.
That is only workable because of the next line: already downloaded images are skipped by default. Without that, re-ripping an album would re-download everything.
The remaining entries are narrower. There is a built in updater. Albums on e-hentai and nhentai containing certain tags can be skipped automatically, with a wiki page on how to enable it. And a range of URLs can be downloaded, with a wiki section on doing it.
So the operational model is: point it at an album URL, it creates a directory of images, and running it again fills in whatever appeared since. That is an archive tool rather than a fetcher, and the naming reflects that.
The build verb runs the tests, which is why build test is the same command
The build section explains the Gradle verbs in a way that saves you a mistake, because the default verb does more than compile.
The `build` verb builds the jar, builds the tests, and also runs the tests, except for disabled and flaky ones. So `build` and `build test` are synonymous, and the readme shows both:
./gradlew build
./gradlew build testTo be specific about which tests run, you pass a filter, as in this example for a change to one site's adapter:
./gradlew clean build testAll --tests XhamsterRipperTest.testXhamster2AlbumThere is a separate `testAll` verb for the excluded tests, which is what the filter above uses. There is also a form that builds without testing at all, `clean build -x test --warning-mode all`, described as useful when you want to see warnings for unchanged files or when an incremental build appears to be interfering with picking up your changes. The readme is careful to add that this should not be an issue with Gradle, so check whether you saved your changes.
`./gradlew assemble` builds the jar without running anything, for manual verification of work in progress.
The changelog is a JSON file and the build scripts are checked in
The changelog is a link to `/ripme.json`, described as the changelog with the file name in bold beside it. So the release history for this project is a JSON file in the repository root rather than a markdown file.
That is a reasonable choice for a project whose releases are automated, since a machine can append to JSON without parsing prose.
The root also carries four shell and batch scripts: `build.sh`, `build.bat`, `remote-branch.sh` and `remote-merge.sh`. The last two names suggest the release flow creates a branch and merges it, which matches the version scheme that records a branch name when a build does not come from main, and the `latest-main` tag used for a development build.
So the repository contains both halves of the pipeline: the Gradle build files, `build.gradle.kts`, `settings.gradle.kts`, the `gradle/` directory and the wrapper scripts, and the release scripts that turn a commit into a tagged jar.
The licence is in `LICENSE.txt` rather than the more usual `LICENSE`, and the root also has `CONTRIBUTING.md` and `SECURITY.md`.
Editorial conclusion
RipMe suits someone archiving public image albums who wants the downloader on their own machine rather than a hosted service, and who is willing to deal with a tool that breaks when a site changes. Check the tag before you trust a build, since the version string tells you the commit count and the SHA, which is more than most jars give you. Expect some rippers to be broken, because the readme lists two as broken now and explains why that is inherent. And follow the readme's advice to search existing issues first, since the project says outright that stale issues remain in two repositories after the merge back.
Frequently asked questions
what is RipMe
RipMe is an album downloader, described as a ripper, for various websites. It is a cross-platform Java tool that runs on your own computer and works on Windows, Linux and Mac, downloading all the images in an online album into a directory. It can re-rip an album to fetch new content and skips already downloaded images by default.
how to install ripme
Download `ripme.jar` from the latest release and run it, with the How To Run wiki page covering the details. Java 21 or later is required. On macOS there is a Homebrew cask, installed with `brew install --cask ripme && xattr -d com.apple.quarantine /Applications/ripme.jar`.
how to use ripme
Run the jar and give it an album URL. It downloads the images, skips ones it already has, and can be run again on the same album to fetch new content. There is a built in updater, a way to download a range of URLs, and a config option to skip e-hentai and nhentai albums carrying certain tags. Search existing issues before reporting anything, since stale issues remain after development moved back from the second repository.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ripmeapp-ripme)Star history chart for your README
[](https://hysenlabs.com/projects/ripmeapp-ripme)Was this useful?