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
|| 3.0.0.alpha35 2.25.32
|| 2.25.2 2.25.1 2.25.0 2.24.3 2.24.2 2.24.0 2.23.0 2.22.0 2.21.2 2.21.1 2.21.0 2.20.3 2.20.2 2.20.1 2.20.0 2.19.0 2.18.1 2.18.0 2.17.0 2.16.1 2.16.0 2.15.0 2.14.0 2.13.4 2.13.3 2.13.2 2.13.1 2.13.0 2.12.1 2.11.0 2.10.0 2.9.4 2.9.3 2.9.2 2.9.1 2.9.0 2.8.4 2.8.2 2.8.1 2.8.0 2.7.1 2.7.0 2.6.1 2.6.0 2.5.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.