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
|| 1.9.15▲5 1.9.14▲2 1.9.12▲ 1.9.11▲2 1.9.10▲2 1.9.9▲2 1.9.8▲3 1.9.7▲3 1.9.6▲ 1.9.4▲ 1.9.3▲2 1.9.2▲ 1.9.1▲4 1.9.0▲ 1.9▲ 1.8.29▲2 1.8.28▲4 1.8.27▲5
|| 4.5.1 4.4 4.23 4.12
|| 3.39 3.2▲11 3.17 3.02 2.12▲2 2.112 2.108 2.9▲2 2.83 2.7▲3 2.6▲ 2.0▲
- 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.