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.012 1.0.3114 1.0.30▲5 1.0.292 188.8.131.52 184.108.40.206 1.0.28▲20 1.0.27▲4 1.0.26▲3 1.0.25▲9 1.0.24▲ 1.0.23▲ 1.0.22▲ 1.0.21▲ 1.0.20▲2 1.0.13▲
|| 9999 1.1.0.r30.g005a36b4 1.0.28 2019-04-21-25824cb9 2019-01-01-42132c54 1.2.0+git20221225.1.a9be96f
- 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.