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
Project |
Spr |
Newest |
Outdated |
Ignored |
Rank |
acpica∗
|
28 |
202303314 |
202210222 202210206 2022033110 202112172 202109305 202106042 20210331 20210105 202012172 20201113 202009253 20200717 20200528 202004302 20200110 20191213 201905096 20190405 201812134 20180810 201806292 20180531 20180427 20180209 201801053 20170831 20170303 20170119 20161222 201609302 201605272 20160108 20150619 20141107 20140926 20140214 20130823 20130517 20080701 |
|
100.0 |
iasl∗
|
12 |
20230331 |
20211217 20210730 20210331 202009252 20200717 20190509 20100915 20090422 200901232 20081204 2022.03.31 2021.12.17 |
|
100.0 |
rust:libacpica∗
|
1 |
0.0.8 |
|
|
84.95 |
Legend:
- 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.