# Elm Packages Registry Scraper (`parseforge/elm-packages-scraper`) Actor

Scrapes Elm package records from the official registry, filtered by search query. Returns each package as a flat row with name, summary, version, license, and author.

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

## Pricing

from $19.00 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner.jpg)](https://apify.com/parseforge?fpr=vmoqkp)

### Elm Packages Registry Scraper

**Scrape Elm package metadata from the official registry, filtered by search query, up to a million packages per run.** Each package comes with its name, summary, version, license, and author. No login or API key. Export to CSV, JSON, Excel, or XML.

The Elm Packages Registry is the central catalog for Elm libraries, but browsing it manually is slow and there is no official bulk export. This Actor reads the public package index directly, filters by a case-insensitive search query, and returns each match in one fixed schema. You get a clean dataset of package names, summaries, versions, licenses, and authors, ready for analysis or tooling.

| Who uses it | What they scrape Elm Packages Registry for |
|---|---|
| Elm developers | Find all packages that match a keyword for a new project dependency |
| Package maintainers | Monitor the registry for naming conflicts or similar packages |
| Researchers | Analyze the Elm ecosystem's growth and package metadata trends |
| Tooling builders | Seed a local package index or IDE autocomplete with registry data |

### What it does

This Actor collects Elm package records from the official registry, filtered by an optional search query, and returns each package as a flat row.

- 🔍 **Search query filter:** case-insensitive substring match on package name and summary, so you get only relevant packages.
- 📦 **Bulk export:** list all Elm packages by leaving the query empty, up to the maximum you set.
- ⚙️ **Flexible limits:** set maxItems from 1 to 1,000,000 to control dataset size and cost.
- 📄 **Flat row output:** each package is one record with name, summary, version, license, and author, ready for spreadsheets.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with Elm Packages Registry data

**🔎 Discover packages by keyword.**

An Elm developer searches for 'json' to find every JSON-related package, then compares summaries and authors to pick the best library.

**📊 Analyze the Elm ecosystem.**

A researcher scrapes all packages to count licenses, track version releases, and map author networks over time.

**🛠️ Build a local package index.**

A tooling engineer exports the full registry to power an offline documentation site or IDE autocomplete.

**🚨 Monitor for naming conflicts.**

A package maintainer runs a weekly scrape for their package name to spot similar or conflicting packages early.

### Why choose this scraper

|  | What you get |
|---|---|
| **No API key** | Reads the public registry directly, no registration or tokens |
| **Fixed schema** | Every package returns the same fields for easy merging |
| **Scalable** | From a quick preview of 10 items to a full registry dump |
| **Export ready** | Save results as CSV, JSON, Excel, or XML with one click |

### How it compares

No other Store actor targets Elm Packages Registry the same way, so the honest comparison is with the alternatives teams actually weigh.

| | Elm Packages Registry Scraper | Build it in-house | By hand |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Elm Packages Registry changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |

### Configure the run

Drive the Actor with an optional search query and a maximum item count. The query is matched against package names and summaries as the registry is read, so only matching packages reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

```json
{
  "maxItems": 10
}
```

A larger pull:

```json
{
  "maxItems": 200
}
```

### Pricing

Pay-per-result: **$0.021 per result** collected. You pay only for the results written to your dataset.

| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [Elm Packages Registry Scraper](https://apify.com/parseforge/elm-packages-scraper?fpr=vmoqkp).
3. Set your inputs and any filters, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to Elm Packages Registry through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=parseforge/elm-packages-scraper"
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**Why am I getting no results?**

Your search query may not match any package name or summary. Try a shorter or more common term, or leave the query empty to list all packages.

**Why did the run stop at 10 items?**

Free users are limited to 10 items for preview. Upgrade to a paid plan to set maxItems higher.

**The dataset is missing some packages I expected.**

The registry may have changed since your last check. Re-run the Actor to get the latest list, and ensure your query is not too restrictive.

**Can I get more fields than name and summary?**

The Actor returns all available registry metadata for each package, including version, license, and author. Check the sample output for the full field list.

### FAQ

| Question | Answer |
|---|---|
| Do I need an API key or login? | No. This Actor reads the public Elm Packages Registry directly, so no authentication is required. |
| What does the search query match against? | The query is a case-insensitive substring match against each package's name and summary. For example, 'http' matches packages with 'http' in either field. |
| Can I scrape all Elm packages? | Yes. Leave the search query empty and set maxItems high enough to list every package in the registry. |
| What is the maximum number of packages I can get? | Paid users can set maxItems up to 1,000,000. Free users are limited to 10 items for preview. |
| What fields are returned for each package? | Each row includes the package name, summary, latest version, license, and author, among other registry metadata. |
| How do I export the results? | After the run, you can download the dataset as CSV, JSON, Excel, or XML from the Apify platform. |
| Is the data live or cached? | The Actor reads the registry at run time, so you get the current package list and metadata. |
| Can I filter by author or license? | The input only supports a search query on name and summary. For other filters, you can post-process the exported dataset. |
| How fast is the scraping? | The registry is small and the Actor is lightweight, so a full scrape typically completes in seconds to a few minutes. |
| What if I get no results? | Check your search query for typos or try a broader term. The query is case-insensitive but must match a substring of the name or summary. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Elm Software Foundation. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

## `searchQuery` (type: `string`):

Optional. Case-insensitive substring matched against each package's name and summary (for example json, http, parser). Leave empty to list all Elm packages.

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

Free users: Limited to 10 items (preview). Paid users: Optional, max 1,000,000

## Actor input object example

```json
{
  "maxItems": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "searchQuery": "",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/elm-packages-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 = {
    "searchQuery": "",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("parseforge/elm-packages-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 '{
  "searchQuery": "",
  "maxItems": 10
}' |
apify call parseforge/elm-packages-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/elm-packages-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/VEaCPilGKXcnn1MqB/builds/rSb4qLKn8FL2haJSr/openapi.json