packhack doesn't yet scrape the following URLs:

Honestly I'd first like to better understand the itch that packhack wants to scratch. When looking up a required functionality for a given Scheme, up to now I never first tried to check one of these generic package lists; instead I use (except for Racket, where all that is easier - but Racket is probably no target for packhack) the implementation's list of supported SRFIs, the contributed packages and ... Google. I always start this search with the expectation that it can cost me a few hours until I either know that I can re-use something existing or not - so the additional value of a package collection (outside the sources just listed: SRFIs and contributed packages - and since I understood the worth of the SRFIs, I started to work on my SRFI-collector) for me is very much limited, since there are so many additional parameters that determine whether an external package can be used for a given version of a given Scheme implementation, that just finding a one-liner description of the package functionality is just to few information to decide whether the package is of any worth.

And whether it takes me 30 seconds or 3 minutes to find that first hint will not make a difference if afterwards I anyway need to spend 30 minutes to 3 hours for a detailed investigation.

But maybe my workflow as described above is just wrong - and experienced Schemers know that e.g. relying on snowfort works. At my whole workplace there is no other Schemer (that I'm aware of), so I just have no idea how other people are using Scheme.

Wait, it seems like most (or all?) of slib is already packaged in Snow-Fort / Akku. So maybe it's not useful to index it separately?

To contribute also at least a bit of concrete information: snowfort lists around 50 packages, theschemer more than 100. A simple mapping of names between these package collections will not work, but some external mapping is required (e.g. theschemer: tsort.scm -> snowfort: slib topological sort). That's all doable, but I think that the infrastructure for these package collections is just much weaker than it is for the SRFIs, so more effort has to be spend to fill in the missing pieces.