# Docker Image Tag Monitor - Digests & Platform Changes (`maydit/docker-image-tag-monitor`) Actor

Monitor exact Docker Hub image tags for digest, architecture and size changes. Compare saved observations before updating a deployment. Public metadata only; no image downloads.

- **URL**: https://apify.com/maydit/docker-image-tag-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 saved observations

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 Image Tag Monitor - Digests & Platform Changes

**See exactly which digest or platform metadata changed between observations without downloading container layers.**

Watch exact public Docker Hub tags for digest, architecture and size changes. Compare saved observations with source links and readable reports. No image downloads or registry credentials.

### Start in under a minute

1. Paste image tags into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose **Start**.
3. Open **Observations**, **Scope and diagnostics**, or the **Readable run report** in Output. Export CSV or JSON from the dataset.

```json
{
  "imageTags": [
    "library/node:lts"
  ],
  "maxResults": 5
}
```

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

### Who this helps

Platform teams reviewing mutable tags before builds or deployments.

### What you receive

One row per unique confirmed observation. Every row includes a stable `recordId`, title, source URL and observation time.

| Field | Meaning |
|---|---|
| `repository` | Source-reported repository; missing optional values remain null. |
| `tag` | Source-reported tag; missing optional values remain null. |
| `digest` | Source-reported digest; missing optional values remain null. |
| `lastPushedAt` | Source-reported last pushed at; missing optional values remain null. |
| `sizeBytes` | Source-reported size bytes; missing optional values remain null. |
| `platformCount` | Source-reported platform count; missing optional values remain null. |
| `platforms` | Source-reported platforms; missing optional values remain null. |
| `comparisonStatus` | not_requested, new, changed or unchanged |
| `changedFields` | Fields different from your last saved observation |
| `previous` | Previous saved source values when comparison is enabled |

### Saved comparisons

Enable **Compare with saved observations**, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable **Save only new or changed observations** for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

### Scope and limitations

Exact Docker Hub tags, current metadata only. Platform entries with unknown OS or architecture are preserved. No image layers, vulnerability scan or supply-chain safety verdict.

At most ten input values and thirty saved rows per run. Each input performs one bounded public API request. Responses are capped at 8 MiB and share the run deadline. No authentication bypass, image/package download or code execution is performed. HTTP 429 stops further requests; Stack Exchange backoff/quota signals are respected. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

### Pricing

The configured base price is **$0.001 per saved observation**, plus **$0.00005 per start** at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

### Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

### Examples

1. **Image tags: library/node:lts** — A bounded library/node:lts observation sample. Review source evidence and export rows or compare them in a later run.
2. **Image tags: library/python:3.12-slim** — A bounded library/python:3.12-slim observation sample. Review source evidence and export rows or compare them in a later run.
3. **Image tags: library/nginx:stable** — A bounded library/nginx:stable observation sample. Review source evidence and export rows or compare them in a later run.

### Source and support

[Official source documentation](https://docs.docker.com/reference/api/hub/latest/). This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.

# Actor input Schema

## `imageTags` (type: `array`):

Exact namespace/repository:tag values. Blank uses library/node:lts.

## `maxResults` (type: `integer`):

Global saved-row cap across this run. Does not promise complete source coverage.

## `comparePrevious` (type: `boolean`):

First comparison run establishes a baseline. Reuse the same inputs and snapshot name. One writer per snapshot.

## `onlyChanges` (type: `boolean`):

Enables comparison. An unchanged run can correctly return zero rows.

## `snapshotName` (type: `string`):

1–80 letters, numbers, underscores or hyphens. Use a distinct name for independent workflows.

## `maxRunSeconds` (type: `integer`):

Requests share the remaining time budget. The platform timeout may stop work earlier.

## Actor input object example

```json
{
  "imageTags": [
    "library/node:lts"
  ],
  "maxResults": 5,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 60
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (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 = {
    "imageTags": [
        "library/node:lts"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/docker-image-tag-monitor").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 = { "imageTags": ["library/node:lts"] }

# Run the Actor and wait for it to finish
run = client.actor("maydit/docker-image-tag-monitor").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 '{
  "imageTags": [
    "library/node:lts"
  ]
}' |
apify call maydit/docker-image-tag-monitor --silent --output-dataset

```

## MCP server setup

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

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/xwjdX9n8M8tVkkg5I/builds/s34QM6qch4IqZhs8m/openapi.json