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.
3 project(s) on this page
2.9.76 2.9.66 2.9.4 2.9.2 2.8.03 2.7.0 2.6.02 2.4.0 2.3.42 2.3.2 2.3.0 2.1.2 2.0.12 1.9.1 1.9.0 1.8.33 1.8.2 1.6.5 1.6.42 1.6.22 1.6.1 1.5.5 1.5.42 1.5.3 126.96.36.199~pre-20181030 188.8.131.52~pre-20180217 1.4.25 1.3.122 1.3.8+mod+20161220 1.3.8+githubmod+20150914+fa3fdef 1.3.84 1.3.73 1.2.38pre2 1.2.372
- 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 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.