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.
2 project(s) on this page
|| 1.17.35 1.17.2 1.17.12 1.17 1.16.73 1.16.52 1.16.42 1.16.3 1.16.2 1.16.12 1.16 1.15.42 1.15.3 1.15.2 1.15.1 1.15 1.14.7 1.14.6 1.14.52 1.14.43 1.14.3 1.14.2 1.14.1 1.12.3 1.12.2 1.12 1.10.10 1.10.9 1.10.8 1.10.7 1.10.6 1.10.5 1.10.4 1.10 1.9.10 1.9.9 1.9.7 1.9.5 1.9.2 1.9.1 1.9 1.8.14 1.8.13 v1.17.4 v1.17.3
- 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.