The October release of Cookbooks added some more programs, improved the already existing ones, and factored out the feedback-related part into another class of the project sanitize_cookbook_dataset. The big work happened in August and September 2015 though, as you can see from the release dates which were not very active in the months before August 2015. The cookbooks project now has more features, more cookbooks, and a better tested codebase. The project currently has exactly 2817 "cookbooks" registered as of November 2015, and it is still growing, albeit at a much slower pace than it did grow 10 years ago. The reason is two-fold - the more cookbooks were added, the fewer can be added, since the amount of available programs is a finite one. And the other reason is that I am investing less time into the project compared to 10 years ago. Still, the project is maintained consistently. You can obtain the amount of registered programs by issuing: cookbooks registered_programs? from the commandline. The Cookbooks Project is a "collection of cookbooks". What does this mean, exactly? A cookbook is essentially a recipe that gives us sufficient information to compile or otherwise install a given program. Examples for this would be the PKGBUILD file in Archlinux, or the various debian controls files for distributions based on Debian. These different programs, the cookbooks, can usually be compiled from source in the event that the source is available - however had, the project also supports the plain installation of projects that do not come with the source, e. g. binary .exe files on windows, or that do not require compilation such as most ruby .gem files, as the latter are just .rb files. How does the format of a cookbook look like? Each cookbook is an individual yaml file which should contain all the required information to get it to install. Another project, class SanitizeCookbookDataset, can be used to visualize this dataset in a colourful manner. To query the information provided by this gem, you can do something such as this here: cookbooks htop This command will invoke the file stored at bin/cookbooks which is part of this project. This file will provide you, in the above example, with information about the program called "htop" (which you should have downloaded from source before, that is; you can specify alternative configurations for the source directory in the configuration file called cookbook_directory.yml). This way the Cookbooks project allows you to build the foundation for a package-manager in Ruby on top of this project. In fact, this is how the Cookbooks project originated itself - I required a separate library that could be used to query program-associated information. Another project, the RBT ("Ruby Build Tools") will then make use of that information. The latest release added "cookbooks last_option?" as commandline instruction, to show the last option used for configure. If you wish to support this project, for now please just test it and report any bugs or lack of documentation. It is still in beta stage and it will take a while before it can stabilize. There is now perhaps a question you may ask - "why would I need this project?" That is a good question and I can not answer it for you, since you have to decide for yourself. In the simplest situation, I have collected a lot of yaml files, more than 2800 different ones, for 2800 different programs. All of this can help you if you wish to use them in one of your projects. So at the "worst case", it simply provides you with lots of individual yaml files, and a ruby wrapper to query or sanitize this information set. I make use of this in RBT when I compile a program, such as "compile htop", which will compile htop for me. If you have specific suggestions on how to make this gem more useful for others or for yourself, please do feel free to drop me an email at: email@example.com Thank you and have fun!