repology.org domain is back up, repology.amdmi3.ru will be discontinued on October 9th
This is (an incomplete) list of repositories not added to Repology after a request, or removed from Repology due to not meeting our requirements (e.g. not being compatible). We'll be glad to add them as soon as they fix the mentioned issues and publish package data in a usable format.
No usable data.
Repository contents gone.
No usable data. Unlike older buckaroo which contained recipes pointing to upstream releases, new buckaroo just forks upstream repositories to add their machinery and Repology cannot extract versions from repositories (yet).
No compatible package names.
No usable data.
No upstream URLs, modules are not prefixed.
No suitable way to fetch data.
No way to fetch just the needed data.
Removed for recurrent incorrect release submissions and then permanent "connection refused" errors.
No usable data.
No longer parses.
No usable data.
No usable data. Also Repology does not support self-contained blobs like flatpaks, which require versions of all bundled components to be considered.
Feed no longer available, replies with HTTP 500.
No usable data (either shell FrugalBuilds, or arch-like metadata with no compatible package names (basenames) and no upstream URLs).
No way to reliably extract name and version from CPV, lack upstream URLs.
Requires complex parser (CMake), does not provide upstream URLs.
Repository data disappeared.
Delisted after data format change. New format involves variable substitutions and requires a complex parser.
No usable data.
No usable data.
No suitable way to fetch data.
No compatible package names.
No usable data, dead.
No usable data.
Requres complex parser (shell).
No usable data.
API requires authorization, no usable data. Also Repology does not support self-contained blobs like snaps, which require versions of all bundled components to be considered.
No upstream URLs, modules are not prefixed.
Requires parsing HTML.
No compatible package names (basenames), no upstream URLs, requires parsing HTML.
Incompatible package names and versions.
No upstream URLs, too little packages.
No usable data.
No suitable way to fetch data, no upstream URLs.
No usable data.