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.3.0+git20220924.1.b60b864 2.3.011 2.2.9 2.2.8 2.2.72 2.2.62 2.2.55 2.2.43 2.2.33 2.2.22 2.2.1 2.1.9 2.1.84 2.1.7▲2 2.1.6▲2 2.1.5▲3 2.1.3▲ 2.1.2▲ 2.1.1▲2 2.1.0▲ 2.0.7▲ 2.0.5▲3 2.0.4▲ 1.1.12▲ 1.1.11▲6 1.1.10▲ 1.1.9▲3 1.1.8▲ 1.1.6▲6 1.1.5▲ 1.0.8▲
- 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.