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.
4 project(s) on this page
|| 2020.0.0alpha1 2012_08_01▲ 93vu 93u_20120801 93u+20120801 93u2 93.20120801 93.u 1.0_20220825_b16c91f0 1.0_20220114_e569f23e 1.0.47 1.0.33 1.0.0 1.0.0-beta2 1.0.0~beta12 20141224 20120801▲5
|| 9999 r1354.6c8b7cb4 20200125-g43d1853 2020.06.30 2020.0.0+20200208 2020.0.0.338.git8d91e8a 2020.0.0.81.git8052490 2020.0.0+really93u+20120801
|| 1.0.3 1.0.0~beta2
- 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.