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.
6 project(s) on this page
| Project |
Spr |
Newest |
Outdated |
Ignored |
Rank |
|
mialmpick∗
|
1 |
0.2.15 |
0.2.14 0.2.13 0.2.11 0.2.10 |
|
100.0 |
|
libmialm∗
|
1 |
1.0.9 |
1.0.8 1.0.7 |
|
93.01 |
|
libvistaio∗
|
1 |
1.2.19 |
1.2.16 |
|
93.01 |
|
mia∗
|
2 |
2.4.7 |
2.4.62 2.4.3 2.2.7 2.2.2 2.0.13 |
|
93.01 |
|
miaviewit∗
|
1 |
1.0.5 |
1.0.4 1.0.2 1.0.1 1.0.0 |
|
93.01 |
|
pymia∗
|
1 |
0.1.9 |
0.1.7 0.1.6 0.1.5 |
|
93.01 |
Legend:
- 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.