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.1.05 1.0.213 1.0.12 1.02 0.24.24 0.24.12 0.24.03 0.23.2▲4 0.23.1 0.22.2.post1▲3 0.22.1▲3 0.21.3▲ 0.20.4▲4 0.20.3▲ 0.20.2▲2 0.20.0▲ 0.19.2▲ 0.19.1▲6 0.19.0▲ 0.18.2▲ 0.18.1▲3 0.18▲ 0.17.1▲ 0.17.0▲ 0.17▲ 0.15.2▲ 0.14.1▲2 0.10.0▲
- Spread means how many repository families (e.g. all Debian versions are 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.