Quicklisp does have a centralized location for archives (hosted on S3), and it statically extracts a lot of useful metadata about project contents and relations

Quicklisp does have a centralized location for archives (hosted on S3), and it statically extracts a lot of useful metadata about project contents and relationships. I'm trying to work with what's available without asking for cooperation from authors. I have lots of ideas for more metadata that can be gathered automatically or semi-automatically. It should be straightforward if time-consuming to set up automatic testing, even if it's as simple as "Does library foo compile and load on implementation bar on operating system baz?" Same with gathering data to answer questions like "What foreign libraries are needed for this project?" or "What is the license for this project?" If you'd like to give the early version a try, drop me an email (xach@xach.com) or visit freenode #quicklisp.