Artifact Hub Packages Scraper

Extract Artifact Hub package metadata from public JSON APIs for Helm charts and other cloud-native packages.

Artifact Hub is where Kubernetes, platform engineering, and cloud-native teams discover Helm charts, operators, policies, plugins, and integrations. This actor turns Artifact Hub search and package detail data into clean Apify datasets you can export, monitor, enrich, or plug into security and vendor-intelligence workflows.

What does Artifact Hub Packages Scraper do?

Artifact Hub Packages Scraper searches Artifact Hub and saves structured package records.

It can collect:

• 📦 Package names, IDs, Artifact Hub URLs, and API URLs
• 🏷️ Package kind, category, repository, and organization metadata
• ⭐ Stars and production organization adoption counts
• 🔐 Security report severity summaries
• ✍️ Signing, signature, deprecation, and verified publisher signals
• 🧩 Keywords, home URLs, links, content URLs, and digest values
• 🐳 Container image metadata exposed by Artifact Hub details
• 🧾 Optional README text and available versions lists

Who is it for?

This scraper is built for teams that need repeatable Artifact Hub package intelligence.

• 🧑‍💻 DevOps engineers tracking Helm chart options
• 🏗️ Platform engineering teams comparing package publishers
• 🛡️ Cloud security teams monitoring signing and vulnerability signals
• 📊 Vendor-intelligence teams mapping cloud-native ecosystems
• 🧪 Data teams building internal catalogs of Kubernetes packages
• 🤖 Automation teams feeding package metadata into alerts or dashboards

Why use this scraper?

Artifact Hub is searchable in a browser, but recurring analysis needs structured data.

This actor helps you:

• Export Artifact Hub search results as JSON, CSV, Excel, or Parquet
• Monitor package deprecation and signing signals over time
• Compare repositories and publishers across package categories
• Feed package metadata into BI, SIEM, or governance workflows
• Avoid writing custom pagination and detail-enrichment scripts

Data you can extract

Field group	Example fields
Package identity	packageId, name, normalizedName, packageUrl, apiUrl
Repository	repositoryName, repositoryDisplayName, repositoryUrl, repositoryId
Publisher	organizationName, organizationDisplayName, verifiedPublisher, officialRepository
Versioning	version, appVersion, availableVersionsCount, optional availableVersions
Popularity	stars, productionOrganizationsCount
Security	securityCritical, securityHigh, securityMedium, securityLow, securityUnknown
Supply chain	deprecated, signed, signatures, containersImages, digest, contentUrl
Metadata	description, keywords, homeUrl, links, artifactHubUpdatedAt, scrapedAt

How much does it cost to scrape Artifact Hub packages?

This actor uses pay-per-event pricing.

• Run start: $0.005 per run.
• Package item: charged only when a dataset record is saved.
• The default input caps the first run to a small, predictable number of packages.

Apify plan tier	Package item price	1,000 packages
Free	$0.000034312	$0.0343
Starter / Bronze	$0.000029837	$0.0298
Scale / Silver	$0.000023273	$0.0233
Business / Gold	$0.000017902	$0.0179
Platinum	$0.000011935	$0.0119
Diamond	$0.000010000	$0.0100

You can control cost with maxItems, by limiting searchQueries, and by turning off detail enrichment for broad discovery runs.

How to scrape Artifact Hub packages

1. Open Artifact Hub Packages Scraper on Apify.
2. Add one or more search queries, such as nginx, postgresql, or prometheus.
3. Choose a package kind, usually Helm charts.
4. Set maxItems to the number of package records you need.
5. Keep detail enrichment enabled if you need links, keywords, containers, or version counts.
6. Run the actor.
7. Export the dataset or connect it to your automation pipeline.

Input configuration

searchQueries

List of Artifact Hub keywords to search.

Examples:

• nginx
• postgresql
• prometheus
• security
• ingress controller

packageUrls

Specific Artifact Hub package URLs or refs to enrich directly.

Examples:

• https://artifacthub.io/packages/helm/bitnami/nginx
• helm/bitnami/postgresql

packageKind

The package kind filter for search mode.

Supported values include Helm charts, Falco rules, OPA policies, OLM operators, Krew plugins, Tekton tasks, KEDA scalers, containers, and all kinds.

maxItems

Maximum package records to save across direct package URLs and search results.

enrichDetails

When enabled, the actor fetches each package detail JSON endpoint. Detail enrichment adds richer metadata but uses one extra HTTP request per package.

includeReadme

When enabled, the actor includes the full package README. Keep this disabled unless you need documentation text, because README fields can be large.

includeAvailableVersions

When enabled, the actor includes full version objects. Keep this disabled unless you need version-level history.

Example input

{
  "searchQueries": ["nginx", "postgresql"],
  "packageKind": "helm",
  "maxItems": 100,
  "enrichDetails": true,
  "includeReadme": false,
  "includeAvailableVersions": false
}

Example output

{
  "packageId": "bec45f52-fe90-46a1-b6eb-a3dcd9bb203f",
  "packageUrl": "https://artifacthub.io/packages/helm/bitnami/nginx",
  "apiUrl": "https://artifacthub.io/api/v1/packages/helm/bitnami/nginx",
  "name": "nginx",
  "packageKind": "helm",
  "repositoryDisplayName": "Bitnami",
  "organizationDisplayName": "Bitnami",
  "version": "25.0.13",
  "appVersion": "1.31.2",
  "stars": 106,
  "deprecated": false,
  "signed": true,
  "securityCritical": 0,
  "securityHigh": 0,
  "productionOrganizationsCount": 2,
  "scrapedAt": "2026-07-07T00:00:00.000Z"
}

Detail enrichment strategy

Search results already include useful fields such as name, description, version, stars, repository, signing, deprecation, and security summary.

Detail enrichment adds fields that usually matter for deeper workflows:

• Keywords
• Home URL
• Links
• Content URL
• Digest
• Container image list
• Available version count
• Optional README

Tips for reliable runs

• Start with one or two search terms and maxItems under 100.
• Use specific project names for focused results.
• Use packageUrls when you already know the packages you want to monitor.
• Disable README and full available versions unless you need large text/history fields.
• Schedule daily or weekly runs for package monitoring workflows.

Integrations and workflows

Security monitoring

Run the actor on critical package lists and alert when deprecated, signed, or security severity counts change.

Platform catalog enrichment

Join package records with your internal service catalog to show approved chart sources, versions, and repository verification flags.

Vendor intelligence

Track repositories, organizations, verified publishers, and production organization counts for cloud-native ecosystem research.

BI dashboards

Export the dataset to Google Sheets, BigQuery, Snowflake, or your warehouse through Apify integrations.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/artifact-hub-packages-scraper').call({
  searchQueries: ['nginx'],
  packageKind: 'helm',
  maxItems: 100,
  enrichDetails: true
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/artifact-hub-packages-scraper').call(run_input={
    'searchQueries': ['nginx'],
    'packageKind': 'helm',
    'maxItems': 100,
    'enrichDetails': True,
})
print(run['defaultDatasetId'])

cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~artifact-hub-packages-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"searchQueries":["nginx"],"packageKind":"helm","maxItems":100,"enrichDetails":true}'

MCP usage

Use this actor from Claude through the Apify MCP server.

Setup for Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=automation-lab/artifact-hub-packages-scraper"

Setup for Claude Desktop, Cursor, or VS Code:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=automation-lab/artifact-hub-packages-scraper"
    }
  }
}

Example prompts:

• "Scrape Artifact Hub Helm packages for nginx and summarize signing status."
• "Find PostgreSQL Helm charts and list verified publishers."
• "Monitor these Artifact Hub package URLs and report deprecated packages."

Scheduling the scraper

Artifact Hub package metadata changes over time as charts update, publishers change, and security reports refresh.

Useful schedules:

• Daily for critical package allowlists
• Weekly for platform catalog refreshes
• Monthly for broad vendor-intelligence snapshots

Data quality notes

The actor reads Artifact Hub public API responses. Empty or missing fields usually mean Artifact Hub did not expose that value for a package.

The scrapedAt field is the collection timestamp. The artifactHubUpdatedAt field comes from Artifact Hub package metadata when available.

Performance notes

This is an HTTP/API actor. It does not launch a browser and does not require a proxy for normal operation.

Detail enrichment performs one additional request per package. For very broad searches, increase maxItems gradually and disable optional large fields unless needed.

Legality and responsible use

Artifact Hub package pages and JSON endpoints are publicly accessible. Use the scraper responsibly, respect Artifact Hub availability, and only process data for legitimate business, research, security, or engineering workflows.

You are responsible for how you use exported data and for complying with applicable laws and policies.

FAQ

How fast is Artifact Hub Packages Scraper?

Most HTTP-only runs finish quickly. A 120-package run with detail enrichment completed in about 10 seconds during validation.

Does this actor need an Artifact Hub API key?

No. It uses Artifact Hub public JSON endpoints that are available without login, browser automation, or a paid API key.

How much does an Artifact Hub scraping run cost?

Cost depends on saved package records. The actor charges a small run-start event plus a low per-package item event shown in the pricing table above.

Why did I get fewer records than maxItems?

Artifact Hub may return fewer matching packages for your query and package kind. Try broader keywords or set packageKind to all.

Why are README or versions missing?

includeReadme and includeAvailableVersions are disabled by default to keep rows compact. Enable them when you need those fields.

Why are some security fields empty?

Artifact Hub does not expose complete security summaries for every package. Missing values reflect the upstream API response.

Related scrapers

Explore other Automation Lab actors for cloud, developer, and security workflows:

• https://apify.com/automation-lab/github-repositories-scraper
• https://apify.com/automation-lab/docker-hub-scraper
• https://apify.com/automation-lab/website-contact-finder

Changelog

0.1

Initial version with Artifact Hub search, direct package URL enrichment, Helm-first defaults, security/signing metadata, repository metadata, and optional README/version fields.

Support

If you need a new Artifact Hub field, a different output shape, or a workflow-specific integration, open an issue on the Apify actor page with an example package URL and desired output.