feedstocks

What the repository is

This repository is an automated summary of all the individual package feedstocks that make up conda-forge. It is explicitly not updated by hand; instead a process collects the separate feedstock repositories, each of which lives in its own repo such as conda-forge/unzip-feedstock, and presents them together. The result is a single place that lists the full set of conda-forge packages without the reader needing to know each feedstock's individual location. It functions as a directory rather than as a source of packaging logic.

Where to file issues

Because packaging work happens in the per package repos, the README points issue reporters to the right place depending on scope. A problem with one package, say unzip, should go to that package's feedstock issues page. A request to add a brand new package should go to the conda-forge/staged-recipes repository issues. A wider, project level issue should go to the conda-forge.github.io repository issues. This routing keeps the index repo free of package specific discussion and directs contributors to where maintainers actually work.

Why it exists

conda-forge packages number in the thousands, and each has its own feedstock repository, build configuration and maintainer set. Without an index, discovering the complete catalog or confirming that a package exists means knowing the feedstock naming convention. This aggregated repository gives a single browsable surface for the whole ecosystem and is licensed BSD-3-Clause. It reflects conda-forge's distributed maintenance model, where no single repo holds every package but the index ties them together.

Editorial conclusion

The repository holds no build logic of its own and is licensed BSD-3-Clause; all actual packaging lives in the individual feedstock repositories it links to.