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.
5 project(s) on this page
|| 2.9.6▲5 2.9.5▲4 2.9.4▲2 2.9.3▲5 2.9.2▲6 2.9.1▲4 2.9.1-RC1▲ 2.9.0▲2 2.8.0▲2 2.7.7▲3 2.7.5▲ 2.7.3▲3 2.6.3▲ 2.1.7▲
|| 3.0.7▲ 3.0.6▲2 3.0.5▲ 3.0.4▲4 22.214.171.124▲ 3.0.3▲2 3.0.2▲ 3.0.0▲2
|| 3.3.22 3.3.03 3.2.3 3.2.02 3.1.0 3.0.2 3.0.03 126.96.36.19960414git 2.2.95 2.2.84 2.2.62 2.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.