Quay.io Container Images Scraper
Pricing
from $19.00 / 1,000 results
Quay.io Container Images Scraper
Scrapes public container image metadata from Quay.io by namespace. Returns each image as a flat row with tags, manifest digest, and last-modified timestamp.
Pricing
from $19.00 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Quay.io Container Images Scraper
Scrape container image metadata from any Quay.io namespace or repository, up to a million per run. Every image comes with its tags, manifest digests, last-modified dates, and security scan status. No API token required. Export to CSV, JSON, Excel, or XML.
Quay.io hosts millions of public container images, but browsing them through the web UI is slow and the registry API requires pagination handling. This Actor reads the public catalog and repository feeds directly, filtered by namespace, and returns each image in one fixed schema so you can audit, catalog, or monitor images at scale.
| Who uses it | What they scrape Quay.io for |
|---|---|
| DevSecOps engineers | Audit public images in a namespace for outdated base layers or missing security scans. |
| Platform teams | Catalog all images under an organization namespace for an internal developer portal. |
| Open-source maintainers | Track tag history and manifest changes across project repositories. |
| Compliance officers | Verify that public images have a recent last-modified date as part of a supply-chain checklist. |
What it does
This Actor collects container image records from Quay.io by namespace and returns each one as a flat row with its tags, digest, and modification timestamp.
- π·οΈ Tag and digest collection: each image row includes its full tag list and manifest digest for precise pinning.
- π Last-modified tracking: the last-modified timestamp is captured so you can spot stale or abandoned images.
- π Namespace filter: limit the scrape to a single organization or user namespace to stay focused.
- β‘ No authentication: reads only the public catalog and repository endpoints, no API key or login needed.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Quay.io data
π‘οΈ Audit public images for stale content.
A DevSecOps engineer scrapes an organization namespace every month, filters by last-modified date, and flags images older than 180 days for the maintainers.
π Build an internal image catalog.
A platform team scrapes all namespaces used by their engineering org, exports the dataset to a CSV, and imports it into Backstage as a software catalog entry.
π Monitor tag mutations.
An open-source maintainer runs the Actor weekly on their project namespace, diffs the tag-to-digest mapping, and alerts on unexpected manifest changes.
π Feed a compliance dashboard.
A compliance officer scrapes the namespace, loads the JSON into a dashboard, and verifies that every production image has been pushed within the retention window.
Why choose this scraper
| What you get | |
|---|---|
| Tag and digest inventory | A flat list of every image, its tags, and its current manifest digest. |
| Last-modified date | The timestamp of the most recent push, so you can find unmaintained images. |
| Namespace scoping | Collect only the images that belong to one organization or user. |
| Flat structured output | Every image is one row, ready for CSV, JSON, Excel, or XML export. |
How it compares
No other Store actor targets Quay.io the same way, so the honest comparison is with the alternatives teams actually weigh.
| Quay.io Container Images Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Quay.io 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 from a Quay.io namespace and set a maximum item count, and the namespace filter runs as each image is read so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
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 to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Quay.io Container Images Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Quay.io through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting zero results?
Check that the namespace name is spelled exactly as it appears in the Quay.io URL. The namespace is case-sensitive. Also confirm the namespace has public repositories.
The run stopped before reaching my maxItems.
The namespace likely has fewer public images than your maxItems value. The Actor stops when it exhausts the public catalog for that namespace.
Some images are missing tags or digests.
A repository may exist but have no pushed tags yet. The Actor returns whatever metadata Quay.io's public API provides; empty tag lists mean the repository is empty.
The run is taking a long time.
Large namespaces with many repositories require paginated API calls. Quay.io may also throttle requests. Reduce maxItems or run during off-peak hours.
I get a 404 or authorization error.
The namespace may be private or may not exist. This Actor only reads public namespaces. Verify the namespace is accessible in an incognito browser window.
FAQ
| Question | Answer |
|---|---|
| Do I need a Quay.io account or API token? | No. This Actor reads only the public catalog and repository endpoints, which do not require authentication. Private repositories are not accessible. |
| What is a namespace on Quay.io? | A namespace is an organization or user name that groups repositories. For example, 'redhat' or 'bitnami' are namespaces. You provide this in the input to scope the scrape. |
| How many images can I scrape in one run? | You set the maximum in the input, from 1 up to 1,000,000. The Actor stops when it reaches that count or when the namespace has no more public images. |
| Does this Actor download the container images themselves? | No. It collects only metadata such as tags, digests, and timestamps. It does not pull or store image layers. |
| Can I scrape multiple namespaces at once? | One namespace per run. To scrape several namespaces, run the Actor multiple times with different namespace inputs, or use an array input in a wrapper Actor. |
| What output formats are supported? | The dataset can be exported to CSV, JSON, Excel, or XML from the Apify Console or via the API. |
| Does it capture security scan results? | The Actor captures the scan status field that Quay.io exposes in its public API. The actual vulnerability details are not included in the public endpoint. |
| How do I find the correct namespace name? | Visit quay.io/organization/namespace in your browser. The part after 'quay.io/' in the URL is the namespace you should enter. |
| Can I filter by image name or tag inside a namespace? | The namespace filter scopes the whole run. For finer filtering by image name or tag, you can post-process the dataset after the run completes. |
| Is there a rate limit on Quay.io? | Quay.io's public endpoints are rate-limited. The Actor respects standard HTTP backoff, but very large runs may take longer if the server throttles requests. |
Related actors
Browse the full ParseForge collection 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 Red Hat, Inc. 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.
