# Docker Hub Container Images and Tags Sentinel (`adaptive_nightmare/docker-hub-image-radar`) Actor

Monitor container image repositories, official builds, download pull counts, star ratings, operating system architectures, and tag update histories across Docker Hub.

- **URL**: https://apify.com/adaptive_nightmare/docker-hub-image-radar.md
- **Developed by:** [Darim Quraishi](https://apify.com/adaptive_nightmare) (community)
- **Categories:** Developer tools, Open source, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.95 / 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/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 Container Images and Tags Sentinel

Monitor public container images, official registry builds, download pull counts, star ratings, and supported CPU architectures across Docker Hub.

### Features

- Queries public Docker Hub repositories for official and community container images.
- Tracks download counts, star ratings, update timestamps, and short descriptions.
- Extracts target operating systems and supported CPU architectures (such as amd64, arm64, and s390x).
- Distinguishes between verified official library images and third party namespace builds.
- Operates via public JSON endpoints without Docker login credentials or proxy configurations.
- Outputs structured records suitable for export to JSON, CSV, Excel, or automated infrastructure monitoring systems.

### Input parameters

- Search Keyword: Keyword to query container repositories (for example: postgres, redis, or nginx). Leave empty to query recent updates from a namespace.
- Namespace Filter: Organization or account name (default is library for official Docker distribution images).
- Maximum Repositories: Number of container repositories to retrieve, up to 100. Default is 25.

### Output dataset fields

Each dataset record contains:

- repository: Full repository path (for example: library/postgres or bitnami/redis).
- name: Package or application identifier.
- description: Concise summary describing the container image.
- pullCount: Total container download and pull events recorded on Docker Hub.
- starCount: Total developer star endorsements.
- isOfficial: Boolean indicator denoting official Docker curated images.
- isAutomated: Boolean indicator denoting automated build pipelines.
- architectures: Array of compatible processor architectures.
- operatingSystems: Array of target operating systems (such as linux or windows).
- lastUpdated: ISO formatted timestamp of the most recent image publication.
- dockerHubUrl: Direct link to the repository overview page on Docker Hub.
- scrapedAt: UTC timestamp when the data was extracted.

### Use cases

- DevOps package tracking: Monitor when upstream base images publish new version tags and security patches.
- Market research: Analyze popularity trends, pull counts, and ecosystem adoption among competing open source databases.
- Vulnerability workflows: Feed container release metadata into continuous integration security scanners.
- Catalog building: Assemble internal container catalogs for engineering development environments.

# Actor input Schema

## `query` (type: `string`):

Keyword to search across Docker Hub container repositories (for example: nginx, redis, postgres, ollama, or node). Leave blank to retrieve latest updated images.

## `namespace` (type: `string`):

Repository namespace or organization (for example: library for official Docker images). Used when search keyword is empty.

## `maxImages` (type: `integer`):

Maximum number of container repositories to retrieve.

## Actor input object example

```json
{
  "query": "postgres",
  "namespace": "library",
  "maxImages": 25
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptive_nightmare/docker-hub-image-radar").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("adaptive_nightmare/docker-hub-image-radar").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 '{}' |
apify call adaptive_nightmare/docker-hub-image-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,adaptive_nightmare/docker-hub-image-radar"
        }
    }
}
```

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/lXO1ev601fmOyiGRb/builds/EEWOL73dzYmGOCgbf/openapi.json