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 |
can-utils∗
|
11 |
2025.016 |
2023.035
2021.08.05
2020.12.0
2020.11.0
2018.02.0
1243.6b46063
0.0+git20150902
0.0+git20140227
v2023.03
v2020.12.0
20170830 |
9999
2025.01.r5.gc542c9a |
100.00 |
can-uilts∗
|
1 |
v2019.00.0 |
|
|
96.99 |
canutils∗
|
2 |
2023.03 |
2021.08.0
2020.11.0 |
2025.01 |
96.99 |
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.