Open-source project
conda-forge/feedstocks avatar
conda-forge/feedstocks

conda-forge/feedstocks: an automated index, not a codebase

All conda-forge feedstocks, in one convenient place

73 stars41 forksUnknownBSD-3-Clause

At a glance

What is it?
The conda-forge/feedstocks repository is a machine-generated summary of every package feedstock on conda-forge. It is not where issues, recipes, or builds live, and treating it as such will waste your time.
Who is it for?
Adopt conda-forge/feedstocks if you need a single read-only overview of every conda-forge package feedstock, for example to monitor repository names or automate cross-feedstock checks. Do not use it if you plan to edit recipes, file package issues, or request new packages; those actions belong in the individual feedstock repos, staged-recipes, and the conda-forge.github.io issue tracker.
Can I use it commercially?
Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • conda-forge/feedstocks73 ★ · +1
Star history
Repository2026-08-212026-11-15
conda-forge/feedstocks7273

1 Stars in the last 86 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What this repository actually is

The README is blunt: this repository does not get updated by hand, rather it is an automated summary of all the individual package feedstocks which have their own separate repositories. So conda-forge/feedstocks is a directory, not a workspace. Each real feedstock, such as unzip-feedstock, lives in its own repository. The aggregate repo exists so you can see the whole set in one place. If you came looking for source code or build scripts, you are in the wrong spot. The only content described is the summary structure, and the README gives no details on how the summary is generated or how often it refreshes. That gap matters: you cannot tell from the README whether the list is complete or current at any given moment.

The problem it solves: discovery across hundreds of feedstocks

Conda-forge maintains a large number of package feedstocks, each in its own GitHub repository. If you need an overview, clicking through individual repos is slow and error-prone. This aggregate repository gives you a single URL that lists them all. It is for people who want to browse, script, or audit the full feedstock set without knowing every repository name in advance. The target user is a maintainer, an automation author, or a researcher who needs a machine-readable inventory. It is not for end users who install packages with conda; they never need to touch this repo. The README does not state how many feedstocks exist, so any number you see elsewhere is not confirmed by this material.

How the data flow works: automation, not manual curation

The README says the repository is an automated summary, which implies a pipeline that collects metadata from each individual feedstock repository and writes it into this central repo. The exact mechanism is not described in the README. There is no mention of a bot name, a cron schedule, or a trigger event. What is clear is the direction: individual feedstocks are the source of truth, and this repo is a derived artifact. That means changes to a feedstock, such as a new version or a recipe edit, do not appear here unless the automation runs. If the automation breaks, the summary goes stale silently. The README offers no way to check the freshness other than inspecting the repo history yourself.

Getting started: clone, browse, or ignore

The README gives no installation instructions because there is nothing to install. You can clone the repository with git clone https://github.com/conda-forge/feedstocks.git to get a local copy of the summary. After cloning, you can list the directories or files to see the feedstock names. There are no configuration keys, no build steps, and no commands to run. If you only need to find a feedstock repository, you do not even need to clone: the GitHub web interface shows the same listing. The README points you elsewhere for actual work. For a package issue, go to the specific feedstock's issues page, for example https://github.com/conda-forge/unzip-feedstock/issues. For a new package request, go to https://github.com/conda-forge/staged-recipes/issues. For a broader conda-forge issue, go to https://github.com/conda-forge/conda-forge.github.io/issues. That routing is the practical core of this repository.

The main limitation: a read-only index with no issue tracker

The biggest trap is filing an issue here. The README explicitly redirects package-specific issues to the individual feedstock repos. If you open an issue on conda-forge/feedstocks about a broken build or a missing dependency, you are likely talking to the wrong audience. The repo has no maintainers for individual packages. It also has no mechanism for accepting changes: since it is automated, any manual edit would be overwritten or rejected. The wrong tool scenario is clear: you are a package maintainer who wants to update a recipe. You must work in your feedstock repository, not here. Another limitation is the lack of metadata. The README does not describe what the summary contains beyond the feedstock list. There is no mention of version numbers, dependencies, or build status. If you need those, this repo will not give them to you.

Alternatives: the individual feedstocks and the main website repo

The direct alternative is to go to the individual feedstock repository for the package you care about. For example, the unzip feedstock at https://github.com/conda-forge/unzip-feedstock holds the recipe, the build configuration, and the issue tracker. That is where the real work happens. The difference in approach is granularity: the aggregate repo gives you breadth, while the individual repo gives you depth. For requesting a new package, staged-recipes is the correct alternative because it is the intake point for new recipes, not the summary repo. For reporting problems that span multiple packages, such as a change in the conda-forge infrastructure, the conda-forge.github.io repository is the right place. Each alternative serves a distinct purpose, and the README makes those boundaries explicit.

Maintenance and license implications

Maintenance cost is low because the repository is automated, but that automation is also a risk. The README does not name the tool or the schedule, so you cannot predict when updates occur. If you fork this repository, you inherit that uncertainty. A fork will not receive updates unless you pull them manually, and since the upstream is automated, your fork will quickly diverge. The license is BSD-3-Clause, which permits reuse with attribution, but this material gives no copyright holder or license text, so check the LICENSE file in the repository before redistributing anything. The practical takeaway is that this repo is a convenience view, not a dependency. You do not install it, and you do not build on it. You use it to find the real feedstock repositories, and then you leave.

Editorial conclusion

Adopt conda-forge/feedstocks if you need a single read-only overview of every conda-forge package feedstock, for example to monitor repository names or automate cross-feedstock checks. Do not use it if you plan to edit recipes, file package issues, or request new packages; those actions belong in the individual feedstock repos, staged-recipes, and the conda-forge.github.io issue tracker. Before relying on it, verify that the summary is current by checking the last commit date and comparing a few entries against their source feedstocks, because the README states it is automated and not hand-maintained, which means staleness is possible if the automation pauses.

Frequently asked questions

What is conda-forge/feedstocks used for?

It is an automated summary of all the individual conda-forge package feedstocks, each of which has its own separate repository. The README states that this repository does not get updated by hand.

Where do I file an issue about one conda-forge package?

In that package's own feedstock repository. The README uses unzip as the example and points at https://github.com/conda-forge/unzip-feedstock/issues, which shows the package name followed by the feedstock suffix.

How do I request that conda-forge add a new package?

Through the issues page at https://github.com/conda-forge/staged-recipes/issues. That is the destination the README names for new package requests, not this repository's tracker.

Where do I report a problem with conda-forge as a whole?

At https://github.com/conda-forge/conda-forge.github.io/issues, which the README gives as the place for wider issues covering more than a single package.

Does conda-forge/feedstocks publish releases?

No, the repository has no GitHub releases. Its top level holds only .gitmodules, LICENSE, README.md, and feedstocks/, and the last push to main is dated 2026-09-28.

Official sources

  1. Official README
  2. Project repository
  3. README
  4. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/conda-forge-feedstocks.svg)](https://hysenlabs.com/projects/conda-forge-feedstocks)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/conda-forge-feedstocks.svg)](https://hysenlabs.com/projects/conda-forge-feedstocks)

Was this useful?