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
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
ansifilter∗
|
12 |
2.145 |
2.137 2.12 2.11 2.103 2.8 2.4 1.15 1.12 1.11 1.7 |
|
|
highlight∗
|
28 |
3.5012 |
3.493 3.47 3.462 3.442 3.432 3.425 3.41 3.39 3.383 3.362 3.31 3.28 3.183 3.132 3.9 3.82 2.4.7 |
autogenerated |
|
libhighlight∗
|
1 |
3.50 |
|
|
|
perl:highlight∗
|
1 |
3.50 |
|
|
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).