Debian is the source of truth, the default branch is dev, and CI runs on GitLab
YunoHost is an operating system aiming to simplify as much as possible the administration of a server. This repository corresponds to the core code, written mostly in Python and Bash.
At a glance
- What is it?
- YunoHost is a server administration system whose core is Python and Bash, distributed as Debian packages named after the Debian release they target. Its Python manifest says outright that it may be out of date, one of its core dependencies is tracked from a branch rather than a release, two libraries are pinned below their second major, and the pipeline runs on a different forge from the code.
- Who is it for?
- YunoHost is a serious choice if you want a single server that administers itself, run by a project funded through public European grants and hosted by several co-operatives, which is a meaningfully different risk profile from a vendor product. Three things to check before you commit a machine to it.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- YunoHost/yunohost2,992 ★ · +15
| Repository | 2026-09-11 | 2026-11-14 |
|---|---|---|
| YunoHost/yunohost | 3k | 3k |
15 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The default branch is the development branch and the pipeline is on GitLab
Three structural facts sit next to each other on this front page and all three are about where the work actually lives.
The first is the default branch. It is dev, and every link to the licence in the page points at that branch rather than at a stable one. So the branch a clone lands on is the branch where development happens.
The second is the pipeline. The one status badge points at GitLab, not GitHub, while the source, the security scanning link and the contributing links all live on GitHub. There is a GitLab directory and a GitLab CI file in the tree as well as the GitHub directory, so both forges are involved.
The third is releases. The three most recent tags are named after the packaging target rather than the software: they are debian/13.0.8, debian/13.0.7.1 and debian/13.0.7. The version number is the Debian release it targets, and the two three-part numbers published on the same September morning, an hour and a half apart, are a same-day correction rather than a feature difference.
The dependency list that matters is the Debian control file
The Python manifest carries a comment above its dependency block that changes how you should read it: these dependencies might not be up to date, and you should see the Debian control file instead.
That is the packaging truth stated plainly. This project is distributed as Debian packages, so the authoritative list of what a YunoHost installation contains is the control file in the debian directory, and the manifest is a convenience for running the code outside the packaging. Anyone auditing what this code depends on has to read the other file, and anyone who installs with pip is using the list its own authors have flagged as unreliable.
The rest of the tree follows the same shape. A debian directory for packaging, a doc directory, a locales directory for translations, and directories named hooks and maintenance, which are the two concepts this system adds on top of a distribution.
A core dependency comes from a branch, and two libraries are capped below major two
One entry in the dependency list is not a version at all. It is a direct reference to a git repository and a branch name, with no tag and no commit. That is the framework layer this code sits on, and installing the project with pip today pulls whatever the head of that development branch contains at that moment.
Two more entries carry upper bounds at the first major version. One validation library is held below version two, and one token library is held below version two with a floor above one. Both are the shape of a codebase written against the first generation of those APIs, which is normal for a project that has been running for years and also means neither can take a major upgrade without a code change.
Two more dependencies are present but commented out, one for desktop bus integration and one for directory services. That is a useful signal: those two features exist in the code's history and are switched off at the packaging level rather than removed, so a build that needs them is a packaging decision rather than a port.
The manifest names two crypto libraries and a dozen system-facing ones
The dependency list is worth reading as an inventory of what an administration system has to touch, because it is unusually broad for a project of this size.
There are two cryptography libraries, a modern one and an older binding, alongside a password hashing library and a public suffix library, which is what a cookie scope check needs. There are three network reachability helpers: one that speaks UPnP for automatic port mapping, one for multicast service discovery, and one for DNS. There is a message queue library, a file type detector built on content rather than extension, a Debian metadata library, an email address validator, a micro web framework, a templating engine, and a process and system information library.
Set against that, the type checking configuration is strict about the parts it controls and relaxed about the parts it does not. Import following is skipped, three directories are excluded outright, and a specific list of public modules that ship no annotations is exempted, with a comment saying one of them does not provide typing yet.
The licence is per component, and the rest is answered on a wiki page
The licence section is one sentence and it contains a delegation. This repository is licensed under GNU AGPL version 3, as other components of YunoHost are, and the sentence links to a community page for those other components.
So the copyleft terms are clear for the core and explicitly not claimed for everything else. For a project whose product is spread across several repositories and an application catalogue, that distinction matters more than it would in a single-tree library, because the licence of the code you install and the licence of the application you install alongside it are answered in two different places.
The strength of AGPL for a server product is also worth stating, since it is the reason a project like this can be sustained by grants rather than by sales: it is the licence that most directly obliges a network service to offer its source, which is what makes the model defensible for a public-interest hosting project.
Issues live in a different repository from the code
The issue tracker link in the introduction does not point at this repository. It points at a separate repository in the same organisation, a repository whose name is just the word for issues, which holds the tracker for the whole project rather than for this code.
The same pattern shows up in the screenshots table, which names three other repositories to describe what the product does: the web administration interface is one project, and the single sign-on user portal is described as a portal project plus a separate authentication component. So the thing a user experiences as one operating system is at least four codebases, and this repository is the one holding the core logic.
The consequence for anyone filing a bug or reading history is simple and worth knowing before you start: the discussions for this code are not in this repository, and neither is the branch history of the components that make the interface.
Two grant agreements with numbers, and a list of supporting hosts
The funding section is the most concrete paragraph in this README, and it is concrete in a way that is easy to skim past. The project was funded successively through two funds established by a Dutch non-profit, with financial support from a European Commission programme, administered by a named directorate, under two grant agreements with numbers.
That is public money with a paper trail, which is a different kind of sustainability from a venture-backed company or a founder-maintained side project, and it explains why the licence is copyleft and why the mission is framed as simplifying administration rather than as a product.
The sponsor block adds the operational half of the same story: seven organisations, including two grant funds, a code cooperative, a network operator, a hosting provider and a small association, thanked for infrastructure as well as money. The wording is thankfulness rather than a service level, but the list tells you the project's servers and its funding come from the same places.
Three ways to contribute, and the translations live in this tree
The contributing section offers three doors and no others. There is developer documentation for getting started with the code, a development chatroom, and a translation platform where contributors can work on localisation.
That third door is backed by the repository itself: there is a locales directory at the root, so translations are versioned alongside the code rather than held in a separate system. For a project translated into a long tail of languages, keeping the strings in the same repository as the strings they describe is a deliberate choice about who can review them.
The rest of the tree is unremarkable in the best way: a bin directory, a configuration directory, a share directory, a source directory, tests, and a Python version file at the root. Nothing in the tree contradicts the claim that this is the core of a larger product, and nothing in it suggests the project is one person's experiment.
Editorial conclusion
YunoHost is a serious choice if you want a single server that administers itself, run by a project funded through public European grants and hosted by several co-operatives, which is a meaningfully different risk profile from a vendor product. Three things to check before you commit a machine to it. Read the community licence page rather than assuming one licence covers the whole product, since this repository explicitly defers the other components. Install from the Debian packages rather than from the Python manifest, because the manifest says it may be stale and pulls one dependency from an unpinned branch. And set expectations about the code itself: the default branch is the development branch and the pipeline runs on a different forge, so a checkout is not the same thing as a release.
Frequently asked questions
what is yunohost
YunoHost is an operating system aimed at making server administration as simple as possible. This repository is its core code, written mostly in Python and Bash, while the web administration interface and the single sign-on portal are separate repositories.
how to install yunohost
Not from this repository, which links to the install documentation and contains none of the steps. What the repository shows is packaging: releases are named after the Debian release they target, the newest being debian/13.0.8, and the dependency truth lives in the Debian control file rather than the Python manifest.
Is yunohost free?
The core code is GNU AGPL version 3. The README also states that other components of YunoHost carry their own licences and links to a community page for those, so the terms of the whole product are not answered by this repository alone.
Is yunohost safe to run a server on?
This repository does not make that claim for itself. It publishes a code scanning link, the licence and the packaging metadata. Questions about running the system safely belong to the documentation and the community, and the repository carries no security advisories of its own.
How does yunohost compare with Docker or a hosted control panel?
The repository makes no such comparison. Its own framing is an operating system for server administration, distributed as Debian packages named after the Debian release, with extensions handled as its own packaging concept rather than as containers.
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/yunohost-yunohost)Star history chart for your README
[](https://hysenlabs.com/projects/yunohost-yunohost)Was this useful?