# Anaconda Conda Package Scraper - Versions & Downloads (`ninhothedev/anaconda-scraper`) Actor

$0.5/1K 🔥 Anaconda/conda scraper! Package versions, downloads, license & platforms. No key. JSON, CSV, Excel or API in seconds. Audit data-science dependencies ⚡

- **URL**: https://apify.com/ninhothedev/anaconda-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Anaconda / Conda Package Scraper

Scrape **conda package data from anaconda.org** — versions, total downloads, license, supported platforms, package types, maintainer channel and project links — with **no API key, no login and no proxy required**.

Point it at `channel/name` pairs like `conda-forge/numpy` or `bioconda/samtools`, or search the whole registry by keyword and get one clean, flat row per package.

***

### What you get

One dataset item per conda package:

| Field | Description |
| --- | --- |
| `name` | Package name, e.g. `numpy` |
| `full_name` | `channel/name`, e.g. `conda-forge/numpy` |
| `channel` | Owning channel / organisation (`conda-forge`, `bioconda`, `anaconda`, …) |
| `summary` | Short description (capped at 1,000 chars) |
| `description` | Long description (capped at 3,000 chars) |
| `license` | SPDX-style license string, e.g. `BSD-3-Clause` |
| `latest_version` | Newest published version |
| `version_count` | Number of published versions |
| `total_downloads` | Sum of downloads across every uploaded artifact |
| `file_count` | Number of uploaded build artifacts |
| `platforms` | Unique subdirs, e.g. `linux-64`, `osx-arm64`, `win-64` |
| `package_types` | e.g. `conda`, `pypi`, `standard` |
| `home_url`, `doc_url`, `dev_url`, `html_url` | Project homepage, docs, repo, anaconda.org page |
| `created_at`, `modified_at` | ISO-8601 UTC timestamps |
| `watchers` | Watcher count on anaconda.org |
| `source`, `scraped_at` | Provenance metadata |

Every field is nullable — community channels publish very sparse metadata and the scraper never invents values.

#### Sample output

```json
{
  "name": "numpy",
  "full_name": "conda-forge/numpy",
  "channel": "conda-forge",
  "summary": "The fundamental package for scientific computing with Python.",
  "license": "BSD-3-Clause",
  "latest_version": "2.5.1",
  "version_count": 115,
  "total_downloads": 145216988,
  "file_count": 3739,
  "platforms": ["linux-64", "linux-aarch64", "linux-ppc64le", "osx-64", "osx-arm64", "win-64"],
  "package_types": ["conda"],
  "home_url": "http://numpy.org/",
  "doc_url": "https://numpy.org/doc/stable/",
  "dev_url": "https://github.com/numpy/numpy",
  "html_url": "http://anaconda.org/conda-forge/numpy",
  "created_at": "2020-06-06T23:22:39.637000+00:00",
  "modified_at": "2026-07-05T00:25:51.477000+00:00",
  "watchers": 1,
  "source": "anaconda",
  "scraped_at": "2026-07-28T12:13:48.770763+00:00"
}
```

***

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | select | `packages` | `packages` = fetch details for given `channel/name` pairs. `search` = keyword search the registry. |
| `packages` | array | `["conda-forge/numpy", "conda-forge/pandas"]` | Packages as `channel/name` (full anaconda.org URLs also work). |
| `queries` | array | – | Search keywords, e.g. `["pytorch"]`. |
| `maxItems` | integer | `100` | Hard cap on dataset items (max 1,000). |

#### Example: track your dependency stack

```json
{
  "mode": "packages",
  "packages": [
    "conda-forge/numpy",
    "conda-forge/pandas",
    "conda-forge/scikit-learn",
    "bioconda/samtools",
    "pytorch/pytorch"
  ],
  "maxItems": 100
}
```

#### Example: discover packages by keyword

```json
{
  "mode": "search",
  "queries": ["pytorch", "bioinformatics", "geospatial"],
  "maxItems": 300
}
```

***

### Use cases

- **Data-science tooling** — keep an internal catalogue of the conda packages your notebooks and pipelines depend on, with live version and platform coverage.
- **Dependency audits** — flag packages whose latest version is stale, whose license changed, or that dropped a platform such as `osx-arm64` or `win-64`.
- **Package discovery** — search the registry for a topic and rank candidates by download volume before committing to a dependency.
- **Open-source intelligence** — benchmark adoption of libraries across `conda-forge`, `bioconda` and vendor channels using download counts and release cadence.

***

### Pricing

Roughly **$0.50 per 1,000 packages**. Runs on 512 MB and hits a public JSON API directly, so there is no browser overhead, no proxy cost and no rate-limit dance.

### Speed & reliability

- Fully async, batched up to 50 packages in flight.
- Chrome 124 TLS fingerprint via `curl_cffi`, with a stdlib `urllib` fallback.
- Retries with exponential backoff on 429/5xx; missing packages are logged and skipped rather than crashing the run.
- Datacenter-clean: works on Apify's default datacenter IPs, no residential proxy needed.

### Notes & limits

- Data comes from the public `api.anaconda.org` endpoints; private channels are not accessible.
- Search returns registry index records, which omit per-file data — in `search` mode `file_count` is `null` and `total_downloads` falls back to the channel-reported aggregate.
- Only public metadata is collected. No personal data, no login, no scraping of gated content.

### Related actors

- [PyPI Scraper](https://apify.com/ninhothedev/pypi-scraper)
- [npms Search Scraper](https://apify.com/ninhothedev/npms-search-scraper)
- [crates.io Scraper](https://apify.com/ninhothedev/crates-io-scraper)
- [Hex.pm Scraper](https://apify.com/ninhothedev/hex-pm-scraper)

***

*Keywords: anaconda scraper, conda package scraper, anaconda.org API, conda-forge data, conda package downloads, package registry scraper, dependency audit, Python package metadata.*

# Actor input Schema

## `mode` (type: `string`):

What to scrape. "packages" fetches full details for the channel/name pairs listed in Packages. "search" runs each keyword in Queries against the anaconda.org search index and returns matching packages.

## `packages` (type: `array`):

Conda packages to scrape, written as "channel/name" (for example conda-forge/numpy, bioconda/samtools, anaconda/scipy). Full anaconda.org URLs are accepted too. Used when Mode is "packages".

## `queries` (type: `array`):

Keywords to search the anaconda.org package index for, for example "pytorch" or "bioinformatics". Each query returns up to 100 matching conda packages. Used when Mode is "search".

## `maxItems` (type: `integer`):

Maximum number of packages to push to the dataset across all inputs. Keeps runs cheap and predictable.

## Actor input object example

```json
{
  "mode": "packages",
  "packages": [
    "conda-forge/numpy",
    "conda-forge/pandas"
  ],
  "queries": [
    "pytorch"
  ],
  "maxItems": 100
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "packages": [
        "conda-forge/numpy",
        "conda-forge/pandas"
    ],
    "queries": [
        "pytorch"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/anaconda-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "packages": [
        "conda-forge/numpy",
        "conda-forge/pandas",
    ],
    "queries": ["pytorch"],
}

# Run the Actor and wait for it to finish
run = client.actor("ninhothedev/anaconda-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "packages": [
    "conda-forge/numpy",
    "conda-forge/pandas"
  ],
  "queries": [
    "pytorch"
  ]
}' |
apify call ninhothedev/anaconda-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ninhothedev/anaconda-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/EyngwPvAW7VkS65eo/builds/id1ayy8Gm6lIShTgq/openapi.json