Related projects are determined by recursively matching package homepage URLs. Note that this list may be incomplete as Repology may not be able to get homepage URLs from some repositories.
4 project(s) on this page
|| 4.11.1+git20220822.1.c77a63b 4.11.1▲9 4.11.02 4.10.23 4.10.16 4.9.05 4.8.0▲2 4.7.0▲2 4.6.7▲3 4.6.6▲2 22.214.171.124+dde▲ 4.6.5▲3 4.6.2▲ 4.6.1▲ 4.5.0▲ 4.4.2▲2 4.4.0▲ 4.3.0▲ 4.2.0▲ 4.1.3▲3 4.1.2▲ 4.0.1▲ 3.2.3▲2
|| 4.19.22 4.19.1 4.19.0 4.18.0 4.17.0 4.16.0 4.15.0 2.247 2.06
- Spread means how many repository families (e.g. all Debian versions as well as Ubuntu and other derivatives make a single family) contain this package.
- newest#repos - newest known version. The number shows how many repository families have this version.
- devel - newest known devel (or unstable) version. There may be both devel and newest versions for a given package.
- unique - package is only present in a single repository family, there are no other sources to compare it against, so although it's the latest version known to repology, is not really reliable.
- outdated - outdated version which requires updating.
- legacy - outdated version when a newer version is present. This is assumed to be legacy version preserved for e.g. compatibility.
- rolling - package is fetched from always latest snapshot or VCS master/trunk, so it is always latest and is not a subject for comparison.
- noscheme - the project does not have official versioning scheme, so versions used in repositories which are basically random.
- incorrect - version is known to be incorrect (e.g. version not officially released yet, or lacking alpha/beta/rc qualifier).
- untrusted - this source is known to likely supply incorrect versions, so is ignored proactively.
- ignored - version is ignored and excluded from comparison for some other reason (e.g. snapshots).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.