Projects

44 project(s) on this page

Project	Selected	Spr	Newest	Outdated	Ignored
btrfs-progs	scm 7.1	2	7.1
composefs	1.0.8	2	1.0.8
convmv	2.05	2	2.06
cryfs	1.0.3	2		0.11.3
cryptsetup	2.8.8	2	2.8.8
ddrescue	1.30	2	1.30
dfc	3.1.1	2	3.1.1
dosfstools	4.2	2	4.2
dutree	0.2.18	1
dysk	3.7.1	1
e2fsprogs	1.47.4	2	1.47.4
ecryptfs-utils	111	2	111
exfatprogs	scm 1.4.3	2	1.4.3
extundelete	0.2.4	2	0.2.4
f2fs-tools	1.16.0	2	1.16.0
facron	1.1	1
fusefs:jmtpfs	scm	2	0.5
fusefs:overlayfs	1.18	2		1.17
fusefs:s3fs	1.97	2	1.97
fusefs:sshfs	3.7.6 2.9	2	3.7.6
fuseiso	20260507	1
gparted	1.8.1	2	1.8.1
incron	0.5.10	2	0.5.12
inotify-tools	3.20.2.2	2	4.25.9.0
libfuse	3.18.3 2.9.9	2	3.18.3	2.9.9
lvm2	2.03.42	2	2.03.43
mdadm	4.6	2	4.6
mtd-utils	scm	2	2.3.1
mtools	4.0.49	2	4.0.49
mtpfs	1.1	1
multipath-tools	0.15.1	2	0.15.1
ncdu	2.9.1 1.20	2	2.11.1
nilfs-utils	2.2.11	2	2.2.11
ntfs-3g	2026.9.28	2	2026.9.28
nwipe	0.42	2	0.43
obexfs	0.11	1
partclone	0.3.18	2	0.3.50
parted	3.7	2	3.8
pydf	10	1
qdirstat	1.7.1	2	2.0
reiserfsprogs	3.6.27	1
squashfs-tools	4.7.5	2		4.7.4
sysfsutils	2.1.1	2	2.1.1
udftools	2.3	2	2.3

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.