Leiningen's GitHub repository is now a Codeberg mirror that only keeps uberjars current
Moved to Codeberg; this is a temporary convenience mirror
At a glance
- What is it?
- The technomancy/leiningen repository on GitHub has become a temporary convenience mirror. Source, discussion and contributions belong on Codeberg, while GitHub stays useful mainly as the download host for release uberjars.
- Who is it for?
- Treat the technomancy/leiningen repository on GitHub as a download location for Leiningen uberjars and nothing more. Anyone who contributes, files issues, builds from source or reads documentation should point at codeberg.org/leiningen/leiningen instead.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Clojure, 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
- technomancy/leiningen7,291 ★ · -5
| Repository | 2026-10-01 | 2026-11-15 |
|---|---|---|
| technomancy/leiningen | 7.3k | 7.3k |
-5 Stars in the last 45 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The GitHub repository is a temporary convenience mirror of Codeberg
The technomancy/leiningen repository on GitHub describes itself as a temporary convenience mirror. The project's home is now https://codeberg.org/leiningen/leiningen, and the README greets visitors with "Hello Github User!" before asking them to switch their git remotes to that Codeberg address. The move links to the Software Freedom Conservancy's Give Up GitHub campaign, and the maintainers explain it in governance terms: Codeberg is operated like a user-owned cooperative with a democratic governance model, and you can log in there with an existing GitHub account.
For anyone who cloned Leiningen years ago, the practical consequence is that a clone pointing at github.com now points at a copy. The word temporary in the repository description means the mirror is not an address to build tooling around. If your fork, CI checkout or vendored submodule still references the GitHub URL, switch it to the Codeberg remote now instead of waiting for the mirror to go away.
Only the uberjars keep updating on GitHub
There is one exception to the move, written as a packagers' note. Downstream maintainers whose scripts download the Leiningen uberjar can keep pulling it from GitHub, because the project continues to host those files there to reduce the load on Codeberg. The same note is blunt about scope: the uberjars are the only thing that will continue to be updated here.
That splits the GitHub repository into two different things. As a download host for release jars it stays current. As a place for code, issues or discussion it is no longer the place of record. A distribution package that builds from source should fetch that source from Codeberg, while a package that repackages the prebuilt uberjar can leave its download URL alone. Mixing the two, for example building from the GitHub tree while pinning to the newest jar, can leave you reading source that trails the jar you actually ship, and patches you prepare against the mirror will not reach the maintainers.
Releases 2.11.2, 2.12.0 and 2.13.0 set the pace of the mirror
The three most recent releases give the clearest picture of how the project moves. 2.11.2 arrived on 2024-02-14, 2.12.0 followed on 2025-09-12, and 2.13.0 landed on 2026-06-08. The last push to the GitHub mirror carries the same date as 2.13.0, 2026-06-08, which fits the packagers' note: the mirror changes when a release jar is published.
The consequence is that the GitHub commit graph is a poor signal of whether work is happening. A quiet mirror between releases says nothing about activity on Codeberg, so judging the project's health from GitHub alone will understate it. NEWS.md sits at the top of the tree and is the file to read before moving from 2.12.0 to 2.13.0. The gap between 2.11.2 and 2.12.0 was more than a year, so a team waiting on a specific fix should check NEWS.md and the Codeberg repository rather than expect a quick point release to appear on GitHub.
leiningen-core, lein-pprint and sample.project.clj sit in separate places
The repository layout shows how Leiningen is assembled without opening a single source file. leiningen-core/ is its own directory beside src/, which separates a core library from the top-level project. lein-pprint/ sits next to it as another self-contained directory. bin/ holds scripts, doc/ holds documentation, resources/ and web/ hold supporting files, and test/ plus test_projects/ hold the tests and the sample projects they run against.
The project's own build is defined in project.clj, and sample.project.clj sits beside it as a reference project file. For a reader trying to understand a setting, sample.project.clj is the file to open first. For someone who wants Leiningen's internals as a library, leiningen-core/ is the boundary to look at. Three CI-related entries also live at the top level, .build.yml, .circleci/ and .github/, so more than one CI configuration is kept in the tree, and the GitHub one is not necessarily the one that gates changes after the move.
Shell and Emacs completion files are not part of the jar download
Three files at the top level exist for command line ergonomics: bash_completion.bash, zsh_completion.zsh and pcmpl-lein.el. The first two target bash and zsh. The third is Emacs Lisp, for completing lein commands from inside Emacs.
Because they are standalone files in the source tree, a setup that only downloads the uberjar from GitHub does not put them in place. You have to copy them from a checkout of the Codeberg repository or rely on a distribution package that installs them. They also sit outside the update promise the packagers' note makes for GitHub: only the uberjars keep being refreshed there, so a completion script copied from the mirror can fall behind tasks added in a later release. If tab completion stops offering a task you know exists, compare your copy of the completion file against the Codeberg tree before suspecting the tool itself.
GitHub reports the license as NOASSERTION
GitHub's license detection shows NOASSERTION for this repository, meaning the scanner did not match the license text to a known identifier. The license text itself is in COPYING at the top level. For dependency audits this has a direct cost: anything that reads the GitHub license field gets no identifier for Leiningen, so the license has to be read from COPYING and recorded by hand rather than taken from a badge or an API field.
The README adds a separate statement that is not a license term but sits right next to the question of reuse. Any use of the project's code by GitHub Copilot, past or present, is done without the maintainers' permission, and they do not consent to use of the project's data in training Copilot or any other language model. Teams assembling training corpora from public repositories should treat that as an explicit objection from the authors and exclude the repository, mirror and Codeberg home alike.
Install and tooling questions get a pointer, not an answer, on the mirror
The GitHub front page spends its length on the relocation and on the case for leaving GitHub. People who arrive asking how to install Leiningen, how to install it on Windows, or how it compares with the Clojure CLI and deps.edn get a link to Codeberg rather than a guide. That is the main cost of landing on the mirror: you get the uberjar and a pointer. The doc/ directory and the Codeberg repository are where installation and usage material has to be found.
For conversation, the project keeps the #leiningen IRC channel on Libera.Chat as the place to discuss issues. The rest of the page argues for alternatives to GitHub in general: Codeberg as perhaps the most polished, Sourcehut for minimalists, a self-hosted Forgejo for the adventurous, and a link suggesting some projects do not need a forge at all. It also tells readers who were put off by GitLab's clunkiness and bugs years ago that much better alternatives exist now.
Editorial conclusion
Treat the technomancy/leiningen repository on GitHub as a download location for Leiningen uberjars and nothing more. Anyone who contributes, files issues, builds from source or reads documentation should point at codeberg.org/leiningen/leiningen instead. Before relying on the mirror, confirm that your scripts fetch the release you expect, currently 2.13.0 from 2026-06-08, and read COPYING yourself, because GitHub reports the license as NOASSERTION.
Frequently asked questions
how to install leiningen
The technomancy/leiningen GitHub mirror continues to host the Leiningen uberjars for downstream scripts, with 2.13.0 as the newest release. The source tree, including bin/ and doc/, lives at https://codeberg.org/leiningen/leiningen.
where is leiningen located
The Leiningen repository now lives on Codeberg at https://codeberg.org/leiningen/leiningen. The GitHub repository technomancy/leiningen is a temporary convenience mirror.
Is the Leiningen GitHub repository still updated?
Only the uberjars continue to be updated on GitHub. The last push to the mirror was on 2026-06-08, the same day 2.13.0 was released.
Where can I discuss Leiningen issues?
The project points users to the #leiningen IRC channel on Libera.Chat. Code and contributions belong in the Codeberg 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/technomancy-leiningen)Star history chart for your README
[](https://hysenlabs.com/projects/technomancy-leiningen)Was this useful?