Projects

2 project(s) on this page

Project	Selected	Spr	Newest	Outdated	Ignored
bash-completion∗	1.3	40	2.1126	2.1011 2.95 2.812 2.75 2.6 2.53 2.4 2.2 2.16 1.34	9999 2.9.r2.g483968cd scm
zabbix∗	2.2.1▲ 1.8.14▲	26	5.2.57	5.2.45 5.2.3 5.2.2 5.0.94 5.0.85 5.0.74 5.0.52 5.0.3 5.0.2▲2 5.0.1▲ 4.4.10▲2 4.4.7▲ 4.2.6▲ 4.2.0▲ 4.0.29▲2 4.0.28▲2 4.0.27▲4 4.0.26▲ 4.0.24▲ 4.0.22▲ 4.0.21▲ 4.0.18▲ 4.0.17▲ 4.0.16▲2 4.0.15▲ 4.0.11▲ 4.0.5▲ 4.0.4▲ 4.0.3▲2 3.4.15▲3 3.4.1▲ 3.2.7▲ 3.2.6▲3 3.2.1▲ 3.0.31▲6 3.0.29▲ 3.0.28▲ 3.0.27▲2 3.0.22▲ 3.0.16▲ 3.0.12▲ 3.0.11▲ 3.0.7▲2 2.4.8▲ 2.4.7▲ 2.4.5▲ 2.2.23▲ 2.2.14▲ 2.2.13▲ 2.2.7▲ 2.2.2▲ 2.0.20▲ 2.0.14▲ 2.0.1▲ 1.8.11▲

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.