Projects

20 project(s) on this page

Project	Selected	Spr	Newest	Outdated	Ignored
cydia-impactor∗	0.9.56	1
futurerestore	r186.2f0686d	2			1.186.2f0686d
futurerestore-m1stadev∗	r199.f42719c5	1
futurerestore-m1stadev-test∗	r265.d2a1e87f	1
futurerestore-s0uthwest	r248.08d0e00	1
idevicerestore∗	1.0.0	14	1.1.1	1.0.12 1.0.011 1.0.0+date=2022-05-22	r663.0b4810f 20200709
igetnonce-s0uthwest	r10.6443eb5	1
img4tool	r185.fc1ccfe	2			1.185.fc1ccfe
libgeneral∗	r33.f571dc2	2	54		1.56.e0d98cb
libirecovery∗	1.0.0	16	1.0.013	1.0.0+date=2022-04-04	1.0.0.r27.ge017429 20200706 1.0.25 1.0.1
libirecovery3∗	1	1
libusbmuxd∗	1▲	36	2.0.231	2.0.2+date=2022-05-04 2.0.13 2.0.0 1.2.219 1.1.02 1.1.0~git20181007.07a493a 1.1.0~git20171206.c724e70f 1.0.10▲11 1.0.9▲2	2.0.2.r18.g2ec53542 scm master 20200615 20200615_c7d7d1a 2021-02-06 2.0.3
mt7630-pcie-wifi-dkms	2.1.1	1
partialzipbrowser	1.0.r26.g7c43bde	1
python:amulet-nbt	1.2.1	2	1.2.1
python:flask-apscheduler	1.12.4	3	1.12.42	1.12.2
python:nbt	1.5.1	2	1.5.1	1.5.0
python:pymctranslate	1.0.12.r0.gbac6952d 1.2.2	2	1.2.2
terser∗	5.14.1	1
ttf-hardcompound	1	1

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 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.