Conda Channels and Package Metadata: coverage and access

What it covers

Geography and granularity

Geography: Use the geography stated by the source; coverage can vary by dataset and release.

Granularity: Map installable data-science, numerical, GPU, and scientific-computing packages across channels; analyze platform/build variants and dependency availability for data products.

Source type: Scientific Python/data package ecosystem

Potential use

Map installable data-science, numerical, GPU, and scientific-computing packages across channels; analyze platform/build variants and dependency availability for data products. Especially valuable for founders building data/ML tooling, scientific software, GPU workflows, notebooks, and reproducible environment products.

Access and cost

Public source

Public channels can be queried/used through conda configuration and package metadata; private channels can require tokens. Each channel/package has its own publisher, license, and redistribution terms.

Cost: Current price was not established in this review; check the provider's access terms.

Update cadence: Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.

• Provider page ↗
• Documentation and access details ↗Check the provider's current terms and instructions before use

Interpret carefully

Limits that affect the decision

Conda is channel-based, so coverage and trust differ by channel; package availability is not equivalent to installs or active usage, and platform/build variants complicate simple package counts.

Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.

This record summarizes source documentation; Jon Bishop did not conduct an independent audit of the underlying dataset.