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
Project |
Spr |
Newest |
Outdated |
Ignored |
Rank |
joblib∗
|
1 |
0.17.0 |
0.14.0 0.13.2 0.13.0 0.11 0.10.3 0.10.3git55 0.9.4 0.8.3 0.7.1 0.5.4 |
|
100.0 |
python:joblib∗
|
22 |
1.0.18 |
1.0.05 0.17.03 0.16.03 0.15.12 0.14.15 0.14.0 0.13.24 0.13.02 0.12.4 0.12.2 0.113 0.10.0 0.9.0b4 |
|
100.0 |
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.