# Docker Hub Repository Scraper (`axiomworks/docker-hub-image-scraper`) Actor

Collect Docker Hub repository records through keyword searches, publisher listings or direct lookups. Results include repository names, publishers, descriptions, pull and star counts, update dates and official status; optionally include recent tags and their architectures.

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

## Pricing

from $2.67 / 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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Docker Hub Image Scraper

**Returns:** one row per Docker Hub repository with repository, publisher, description, pullCount, starCount, lastUpdated, isOfficial and tags.
**Input:** `{"searchQueries": ["postgres"], "maxItems": 10, "includeTags": true, "maxTagsPerRepo": 3}`
**Best for:** container image catalogues, tracking pull and star counts over time, finding fresh and popular images.

```json
{
  "id": "library/postgres",
  "sourceUrl": "https://hub.docker.com/v2/repositories/library/postgres/",
  "repository": "library/postgres",
  "description": "The PostgreSQL object-relational database system provides reliability and data integrity.",
  "pullCount": 11882301384,
  "starCount": 15033,
  "lastUpdated": "2026-10-07T22:07:37.55173Z",
  "isOfficial": true
}
```

The local search-URL check returned `library/alpine` with tag `latest`. One platform entry from that run was:

```json
{
  "architecture": "amd64",
  "os": "linux",
  "variant": null,
  "digest": "sha256:d56c381f961d307a21b3ca004cf1e3910f106644aefb1f43e654c8a56c4fd395",
  "size": 3849738,
  "lastPushed": "2026-09-17T23:24:21.672705237Z",
  "lastPulled": "2026-10-15T23:59:50.236887877Z"
}
```

### What does Docker Hub Image Scraper do?

Docker Hub Image Scraper collects public image repository data from Docker Hub and returns it as clean, structured records. You can search images by keyword, list every public repository of a publisher such as an organisation or a user, or look up a list of specific images by name or URL. Each record carries the repository name, publisher, short description, pull count, star count, last update time, official flag, registration date, Docker Hub categories and, if you ask for it, the most recently updated tags with the architectures they were built for.

No Docker login or access token is needed. Public API requests are paced at two per second with retries. This Actor is not affiliated with or endorsed by Docker, Inc.

Typical uses of the data:

- Compare the pull count and star count of images, and rerun the Actor on a schedule to build your own history.
- Build a catalogue of every public image published by one organisation, for example a vendor you depend on.
- Find which images are Docker Official Images and which are community builds, using the official flag.
- Check how fresh an image is by reading its last update time and the update time of its latest tags.
- Read the architectures listed for each recent tag, such as linux/arm64, to see which platforms it was built for.
- Feed a list of image names into a dashboard, a spreadsheet, a database or a language model pipeline.

### What data can you get?

Every record has a stable `id` (the repository name in `namespace/name` form) and a `sourceUrl` that tells you which API endpoint the data came from. Official images such as nginx live in the `library` namespace, so their id is `library/nginx`.

| Field | Type | Description |
|---|---|---|
| `id` | string | Stable identifier, `namespace/name`. |
| `sourceUrl` | string | API endpoint the record was read from. |
| `url` | string | Public Docker Hub page of the repository. |
| `repository` | string | Full repository name, `namespace/name`. |
| `namespace` | string | Namespace the repository lives in. |
| `name` | string | Repository name without the namespace. |
| `publisher` | string | User or organisation that publishes the image. Official images show `library`. |
| `description` | string | Short description of the image. Some repositories have none. |
| `pullCount` | number | Total number of pulls. |
| `starCount` | number | Number of stars. |
| `lastUpdated` | string | Time of the last push, in ISO 8601 format. |
| `isOfficial` | boolean | True for Docker Official Images. |
| `dateRegistered` | string | When the repository was created, in ISO 8601 format. |
| `categories` | array | Category names Docker Hub lists for the repository, when it has any. |
| `tags` | array | Recent tags, each with `name`, `lastUpdated`, `lastPushed`, `fullSize` (bytes), `digest` and `architectures`. Present when tags are included. |
| `isAutomated` | boolean | True if the repository uses Docker Hub automated builds. |
| `lastModified` | string | When the repository metadata last changed, ISO 8601. |
| `hubUser` | string | Docker Hub account that maintains the repository. |
| `status` | string | Repository status, for example `active`. |
| `fullDescription` | string | Full README text of the repository. Only present when you turn it on. |
| `category` | string | Purpose chosen by an AI processor. Only present when you turn AI classification on and it succeeds. |

Architectures are written as `os/arch` or `os/arch/variant`, for example `linux/amd64` or `linux/arm/v7`. Entries with an unknown platform, which are the attestation manifests that some builds attach, are left out so that the list shows real platforms only.

Search URLs can be supplied in `searchQueries`, for example `{"searchQueries":["https://hub.docker.com/search?q=redis"],"maxItems":1}`. The Actor reads the `q` or `query` parameter; other URL parameters do not apply filters. Use `onlyOfficial`, `minStars` and `minPulls` explicitly to filter results. Ordinary keyword inputs continue to work, and all target forms share the same repository limit.

Each tag now also contains `images`, an array of platform records with `architecture`, `os`, `variant`, `digest`, `size`, `lastPushed` and `lastPulled`. This connects each digest and byte size to its specific platform, rather than requiring callers to infer the relationship from the tag's architecture labels. Unknown attestation platforms are excluded just as they are from `architectures`. Missing platform values are null. These are registry observations, not signature checks or vulnerability assessments.

### How to use Docker Hub Image Scraper

1. Open the Actor and go to the Input tab.
2. Fill in at least one of the three targets: search queries, repositories or publishers (namespaces). You can combine them in one run. Records are de-duplicated, so an image found through two routes is saved once.
3. Set the maximum number of repositories. The run stops as soon as that many records are saved.
4. Decide whether you want tags, the full README text and AI classification. Each of these is optional.
5. Start the run and download the dataset as JSON, CSV, Excel or through the API.

A few details about how each target behaves:

For API and MCP calls, provide at least one target explicitly: the search prefill shown in the Console is not an API default. A small shared `maxItems` limit such as 1 or 10 keeps agent previews short. Set `includeTags` to false when only repository counts and descriptions are needed.

**Search queries.** The Actor calls Docker Hub's repository search and follows the result pages of 100 hits each. The search results do not include the last update time or the registration date, so the Actor makes one extra request per repository to read them. Docker Hub stops answering deep paging requests after roughly the first 10,000 results of a query; the Actor treats that as the end of the results and keeps what it has. The Actor keeps results whose name or short description contains every query word of at least three letters; numeric-only fragments are ignored. This filters unrelated fuzzy matches, including nonsense queries. If your search is broad, narrow it down or split it into several queries.

**Repositories.** Give `namespace/name` such as `grafana/grafana`, a bare official name such as `nginx` (which means `library/nginx`), or a Docker Hub URL such as `https://hub.docker.com/r/bitnami/redis`. A repository that does not exist or is private is skipped with a warning.

**Publishers.** Give an organisation or user name such as `bitnami`. The Actor lists all of its public repositories, 100 per page, and the listing holds counts and dates. The Actor also fetches repository details when the listing omits automated-build status or the maintaining account, so `isAutomated` and `hubUser` are populated when Docker Hub provides them.

### Input

| Field | Type | Description |
|---|---|---|
| `searchQueries` | array of strings | Keywords to search Docker Hub images, for example `postgres`. |
| `repositories` | array of strings | Images to look up: `namespace/name`, a bare official name or a Docker Hub URL. |
| `namespaces` | array of strings | Publisher or organisation names whose public repositories are all listed. |
| `maxItems` | integer | Maximum number of repositories to output, 1 to 10000. Default 50. |
| `includeTags` | boolean | Add recent tags with update time and architectures. Default true. |
| `maxTagsPerRepo` | integer | Number of recent tags per repository, 1 to 100. Default 5. |
| `includeFullDescription` | boolean | Add the full README text as `fullDescription`. Default false. |
| `onlyOfficial` | boolean | Keep only Docker Official Images. Default false. |
| `minStars` | integer | Skip repositories with fewer stars. Default 0 (off). |
| `minPulls` | integer | Skip repositories with fewer total pulls. Default 0 (off). |
| `enrichWithAi` | boolean | Add an AI-chosen `category`. Default false. |
| `proxyConfiguration` | object | Apify Proxy settings. Off by default. |

The three filters (`onlyOfficial`, `minStars`, `minPulls`) are applied before counting, so `maxItems` counts only repositories that pass them.

Example input:

```json
{
  "searchQueries": ["postgres"],
  "maxItems": 10,
  "includeTags": true,
  "maxTagsPerRepo": 3
}
```

Another example that lists a publisher without tags:

```json
{
  "namespaces": ["bitnami"],
  "maxItems": 30,
  "includeTags": false
}
```

And one that looks up named images:

```json
{
  "repositories": ["library/nginx", "grafana/grafana", "https://hub.docker.com/r/bitnami/redis"],
  "includeTags": true
}
```

If none of the three targets is filled in, the run fails with a clear message. If a target finds nothing, for example a nonsense search term or a dead repository name, the run finishes with zero items and a warning in the log. Placeholder or error records are never added to the dataset.

### Output

Each repository becomes one dataset item. This is a real item from a search for `postgres`, shortened to three tags:

```json
{
  "id": "circleci/postgres",
  "sourceUrl": "https://hub.docker.com/v2/repositories/circleci/postgres/",
  "url": "https://hub.docker.com/r/circleci/postgres",
  "repository": "circleci/postgres",
  "namespace": "circleci",
  "name": "postgres",
  "publisher": "circleci",
  "description": "The PostgreSQL object-relational database system provides reliability and data integrity.",
  "pullCount": 510217464,
  "starCount": 35,
  "lastUpdated": "2021-12-18T00:17:52.12949Z",
  "isOfficial": false,
  "dateRegistered": "2017-03-27T16:02:50.357893Z",
  "categories": [],
  "tags": [
    { "name": "9-bullseye-ram", "lastUpdated": "2021-12-18T00:17:51.834178Z", "architectures": ["linux/amd64"] },
    { "name": "9.6-bullseye-ram", "lastUpdated": "2021-12-18T00:17:51.276415Z", "architectures": ["linux/amd64"] },
    { "name": "9.6.24-bullseye-ram", "lastUpdated": "2021-12-18T00:17:50.800576Z", "architectures": ["linux/amd64"] }
  ]
}
```

The overview view of the dataset shows the repository, publisher, description, pull count, star count, last update, official flag, registration date, categories, tags and page URL as a table. Pull and star counts are numbers, so you can sort and filter them directly in a spreadsheet.

### How much does it cost?

The Actor is charged per result: you pay for each repository record saved to the dataset, and runs that find nothing cost nothing for results. When you turn on AI classification, a repository whose category was successfully added is charged as an enriched result. If the AI step fails for a repository, the record is still saved with its normal data and no enrichment charge is made. See the Pricing tab of the Actor for the current rates, because they can change. Setting a low `maxItems` is the simplest way to cap the cost of a run, and the Actor never saves or charges for more records than that limit.

### Use with AI agents (MCP)

You can call this Actor from an AI assistant through the Apify MCP server. Add the Actor to your client configuration like this:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=axiomworks/docker-hub-image-scraper"
    }
  }
}
```

Example prompts:

- "Search Docker Hub for redis images and show me the five with the most pulls."
- "List the public repositories published by bitnami and tell me which were updated this month."
- "Look up grafana/grafana and library/nginx and compare their star counts and latest tag architectures."

For agents, the fields to know are `searchQueries`, `repositories` and `namespaces` for the target, and `maxItems` for the limit, 1 to 10000 with a default of 50.

### Integrations and API

You can run the Actor from code and read the dataset through the Apify API. Use your own token, kept in the APIFY_TOKEN environment variable or sent as an Authorization Bearer header.

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("axiomworks/docker-hub-image-scraper").call(
    run_input={"searchQueries": ["postgres"], "maxItems": 10, "includeTags": True}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["repository"], item["pullCount"], item["starCount"])
```

JavaScript:

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('axiomworks/docker-hub-image-scraper').call({
    namespaces: ['bitnami'],
    maxItems: 30,
    includeTags: false,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((i) => process.stdout.write(`${i.repository}\n`));
```

cURL:

```bash
curl -X POST "https://api.apify.com/v2/acts/axiomworks~docker-hub-image-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"repositories": ["library/nginx", "grafana/grafana"], "includeTags": true}'
```

The Actor also works with Apify schedules, webhooks and integrations such as Google Sheets, Zapier, Make and n8n, so you can refresh your image catalogue on a timetable.

### FAQ

**Do I need a Docker account or token?** No. Only public repositories are read, and nothing behind a login is accessed.

**Why do I get fewer results than I asked for?** Either fewer repositories exist for your input, or a search reached Docker Hub's paging cap of about 10,000 results. Warnings in the run log say which one happened.

**Why is `description` empty for some repositories?** Some publishers never write a description. The field is then null.

**Why is `categories` empty?** Categories are optional labels, and many repositories have none.

**Why is `tags` null?** You turned `includeTags` off, or the tag request failed after several retries. A repository with no tags returns an empty list.

**What does the proxy setting do?** By default the Actor connects directly. If you see rate limit warnings (HTTP 429) in your log, enable Apify Proxy in the input and the Actor will use a fresh proxy session on every retry.

**How fast is it?** Searches need about two to three requests per repository, so a run for 100 repositories with tags takes a few minutes. Publisher listings also need repository detail requests when the list omits automated-build status or the maintaining account.

**Is the AI classification reliable?** It is a quick guess from the name and description only. It uses a third-party AI processor, which receives the repository name and description. Check results before relying on them.

### Is it legal to scrape Docker Hub?

The Actor only collects public information that Docker Hub shows to any visitor without logging in, and it keeps a modest request rate. Public repository metadata such as names, counts and dates is generally not personal data, but a publisher name can identify a person, so handle it according to the privacy law that applies to you. Docker Hub's terms of service may limit automated access, and you are responsible for using the data in line with those terms and with the law in your country. This is not legal advice; ask a lawyer if you plan a commercial use that depends on the data.

### Feedback

If a field is missing, a result looks wrong or you need another kind of data from Docker Hub, open an issue from the Actor page and include the input and the run link. Reports with a concrete example are fixed fastest.

# Actor input Schema

## `searchQueries` (type: `array`):

Search terms or Docker Hub search URLs, e.g. \["postgres", "https://hub.docker.com/search?q=redis"]. URLs supply q or query only; set filters below separately. Supply searchQueries, repositories or namespaces. No default search for API calls. Unmatched or blocked targets produce no rows. Up to about 10,000 results per term; maxItems is shared across targets.

## `repositories` (type: `array`):

Repository strings, e.g. \["grafana/grafana", "nginx", "https://hub.docker.com/\_/postgres"]. Bare names mean library/name. Optional when searchQueries or namespaces is supplied; default \[]. Unknown, private or unavailable repositories produce no rows; check the name or use a public repository.

## `namespaces` (type: `array`):

Publisher names or URLs, e.g. \["grafana", "https://hub.docker.com/u/bitnami"]. Lists public repositories under each publisher. Optional when searchQueries or repositories is supplied; default \[]. Unknown publishers produce no rows; check the publisher spelling.

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

Maximum repositories across all searchQueries, repositories and namespaces combined, 1-10000, e.g. 10; default 50. Duplicate repositories appear once. Filters can produce fewer rows. Tags do not count toward this shared limit.

## `includeTags` (type: `boolean`):

Set true to include recent tags with name, fullSize, digest, lastPushed, lastUpdated and architectures, e.g. true; default true. Adds one request per repository. Set false for metadata only (tags is null). maxTagsPerRepo controls the tag count, not maxItems.

## `maxTagsPerRepo` (type: `integer`):

Maximum recent tags per repository, 1-100, e.g. 3; default 5. Only used when includeTags is true. Returns fewer if the repository has fewer tags; independent of the shared maxItems repository limit.

## `includeFullDescription` (type: `boolean`):

Set true to add fullDescription containing the repository README, e.g. true; default false omits the field. May require one extra detail request per search or namespace result. A missing README is null.

## `onlyOfficial` (type: `boolean`):

Set true to keep Docker Official Images only, e.g. true; default false includes community images. Filtered repositories do not count toward maxItems. If no rows match, set false or choose an official image such as nginx.

## `minStars` (type: `integer`):

Skip repositories with fewer stars than this, e.g. 100. 0 disables the filter. Default 0.

## `minPulls` (type: `integer`):

Skip repositories with fewer total pulls than this, e.g. 1000000. 0 disables the filter. Default 0.

## `enrichWithAi` (type: `boolean`):

Set true to request category classification from a third-party AI processor using the repository name and description, e.g. true; default false. Requires the configured AI service. Successful classifications add category; unavailable or failed enrichment does not prevent repository output.

## `proxyConfiguration` (type: `object`):

Connection settings, e.g. {"useApifyProxy": false} (default). Public Docker Hub API requests run directly by default. Enable Apify Proxy if requests are blocked or rate limited (429). Unavailable targets are skipped; check the target and retry with proxy enabled.

## Actor input object example

```json
{
  "searchQueries": [
    "postgres"
  ],
  "repositories": [],
  "namespaces": [],
  "maxItems": 10,
  "includeTags": true,
  "maxTagsPerRepo": 3,
  "includeFullDescription": false,
  "onlyOfficial": false,
  "minStars": 0,
  "minPulls": 0,
  "enrichWithAi": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "searchQueries": [
        "postgres"
    ],
    "maxItems": 10,
    "includeTags": true,
    "maxTagsPerRepo": 3,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("axiomworks/docker-hub-image-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 = {
    "searchQueries": ["postgres"],
    "maxItems": 10,
    "includeTags": True,
    "maxTagsPerRepo": 3,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("axiomworks/docker-hub-image-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 '{
  "searchQueries": [
    "postgres"
  ],
  "maxItems": 10,
  "includeTags": true,
  "maxTagsPerRepo": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call axiomworks/docker-hub-image-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,axiomworks/docker-hub-image-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/6TTkPQue8Fhilcr9G/builds/l9CTGb1QYapgEDDJr/openapi.json