Maven Central Scraper - Java Artifacts & Versions

Scrape Maven Central in bulk. Extract group ID, artifact ID, latest version, version count, packaging, available extensions, repository and last-update timestamp for any Java or JVM dependency to CSV/JSON. No API key, no login.

---

What does the Maven Central Scraper do?

This Actor turns Maven Central data into a structured dataset. You point it at the whole index or by group or artifact, it walks the result pages one after another, and it writes one clean row per artifact into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

Maven Central is the default dependency source for Java, Kotlin, Scala and every other JVM language, and its Solr search API answers without a key across roughly 660,000 artifacts. The Actor reads that API directly and expands Solr's one-letter field names — g, a, p, ec — into readable columns, so an export is usable without knowing the index's internal schema. Pagination is followed automatically until it runs out of results, hits your page limit or hits your Max items cap, whichever comes first. Every row is de-duplicated across the whole run, so you are never billed twice for the same artifact.

There is no API key, no login and no browser involved. That keeps runs fast and cheap, and it means you can schedule the Actor without worrying about credentials expiring.

Who is it for?

• Platform and build engineers auditing which dependencies a stack pulls in.
• Security teams locating artifacts that have not been released in years.
• Developer-relations teams tracking adoption of competing JVM libraries.
• Market researchers measuring the Java ecosystem.
• Developers building dependency tooling over public registry data.

Use cases

• Export every artifact published under an organisation's group ID.
• Find widely published libraries with no recent release.
• Compare how many versions competing libraries have shipped.
• Build a catalogue of artifacts for a framework or ecosystem.
• Track newly published artifacts on a schedule.

Why use this Maven Central Scraper?

• 🔑 Keyless — no account, no API token, no cookies to paste.
• 📦 13 fields per artifact — everything the source exposes, already typed.
• 📄 Real pagination — it walks page after page instead of returning the first screen.
• 🎯 Precise caps — Max items stops the run exactly where you want it, so the bill is predictable.
• 📊 Export anywhere — JSON, CSV, Excel or HTML, plus the Apify API and integrations.
• 💸 Pay per result — you pay for rows you actually receive, with no platform fees to calculate.

What data can you extract?

Every run produces one row per artifact, with these fields:

Field	Type	Description
coordinate	string	Full Maven coordinate, groupId:artifactId
groupId	string	Maven group ID, usually the publishing organisation
artifactId	string	Maven artifact ID
latestVersion	string	Most recently published version
versionCount	number	Number of versions published
packaging	string	Packaging type, e.g. jar, pom or aar
extensions	string	Published file extensions, separated by a pipe
repositoryId	string	Repository the artifact lives in
lastUpdated	string	ISO timestamp of the most recent publication
artifactUrl	string	Maven Central page for the artifact
query	string	Search query this row came from
page	number	Result page the artifact appeared on
scrapedAt	string	ISO timestamp of extraction

Output example

{
  "coordinate": "org.wso2.carbon.identity.framework:org.wso2.carbon.security.mgt.stub",
  "groupId": "org.wso2.carbon.identity.framework",
  "artifactId": "org.wso2.carbon.security.mgt.stub",
  "latestVersion": "7.11.117",
  "versionCount": 2866,
  "packaging": "bundle",
  "extensions": "-sources.jar | .pom | -javadoc.jar | .jar",
  "repositoryId": "central",
  "lastUpdated": "2026-06-10T16:41:15.000Z",
  "artifactUrl": "https://central.sonatype.com/artifact/org.wso2.carbon.identity.framework/org.wso2.carbon.security.mgt.stub",
  "query": "whole index",
  "page": 1,
  "scrapedAt": "2026-09-21T10:18:44.902Z"
}

How to use

Option A — the whole index

{
  "maxItems": 2000,
  "maxPagesPerSearch": 10,
  "searchQueries": []
}

1. Open the Actor and fill in the first field.
2. Set the page limit and Max items to bound the run.
3. Click Start, then export from the Output tab.

Option B — by group or artifact

{
  "maxItems": 1000,
  "maxPagesPerSearch": 5,
  "searchQueries": [
    "g:org.springframework",
    "a:jackson-core"
  ]
}

Everything in the first field is processed independently, so you can batch several targets into one run and split them apart afterwards.

Input parameters

Parameter	Type	Default	Description
searchQueries	array	[]	Maven Central queries, e.
maxPagesPerSearch	integer	3	How many result pages to walk for each search.
maxItems	integer	500	Stop after this many artifacts.
maxConcurrency	integer	2	Parallel requests.
proxyConfiguration	object	{"useApifyProxy": true}	Proxy used to fetch pages.

Tips for best results

• Leave the query empty to walk the whole index — roughly 660,000 artifacts.
• Solr syntax works as-is: g:org.apache.commons lists one organisation, a:jackson-core one artifact.
• The API caps a page at 200 rows; asking for more silently returns 20, so the Actor never exceeds the cap.
• versionCount next to an old lastUpdated is the clearest abandoned-library signal.
• packaging separates real libraries (jar) from dependency aggregators (pom).
• extensions shows whether sources and javadoc jars were published alongside the binary.
• A coordinate is groupId:artifactId; add latestVersion to get a full dependency line.
• Searches are matched against the index, not downloaded artifacts, so the result count is exact.
• Schedule a weekly run to track what an organisation newly publishes.
• Pair with the npm, PyPI and Packagist scrapers to compare ecosystems side by side.

Run outcomes: an empty result is not the same as a blocked run

A crawl that was refused and a query that genuinely has no matches both produce an empty dataset. Treating them as the same thing makes the output unusable for monitoring, so every run is classified and an unverified emptiness is never reported as success.

Outcome	Run status	Meaning
COMPLETED	Succeeded	Everything requested was fetched and rows were saved.
PARTIAL	Succeeded	Rows were saved, but some pages were unreachable.
EMPTY_RESULT	Succeeded	Pages were fetched and parsed and this query really has no artifacts.
BLOCKED	Failed	Every request was refused with HTTP 403/429/503.
NOT_FOUND	Failed	The source answered 404; check the address or filters.
FETCH_FAILED	Failed	Nothing could be fetched for transport reasons.
INCOMPLETE_NO_ROWS	Failed	Pages were skipped and nothing was saved, so an empty result cannot be trusted.

The rule behind the table: a run that fetched nothing can never finish as Succeeded. Each run also writes a SUMMARY record to the key-value store with pages requested, pages fetched, pages skipped, HTTP request and retry counts, a per-status breakdown, transport errors and the termination reason — so the row count is always reconcilable with what the run actually did.

Integrations

Send results straight into the tools you already use: Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor to run hourly, daily or weekly and have each run append to the same dataset, which is how you build a price or availability history rather than a one-off snapshot.

API usage

Run the Actor and collect results from any language. Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~maven-central-artifact-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxItems": 2000, "maxPagesPerSearch": 10, "searchQueries": []}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/maven-central-artifact-scraper').call({"maxItems": 2000, "maxPagesPerSearch": 10, "searchQueries": []});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/maven-central-artifact-scraper').call(run_input={"maxItems": 2000, "maxPagesPerSearch": 10, "searchQueries": []})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Use with AI agents (MCP)

This Actor is available through the Apify MCP server, so an AI agent can call it as a tool. Point your agent at https://mcp.apify.com and it can run the Maven Central Scraper on demand — for example: "Pull the first 500 artifacts from Maven Central and summarise what you find." The agent receives the same structured rows you would get from the UI.

FAQ

Do I need a Maven Central account or API key?

No. The Actor reads publicly available data only. There is nothing to authenticate and no credentials to rotate.

How many artifacts can I get in one run?

As many as the source exposes. Raise the page limit and Max items together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The source ran out of artifacts. That is normal for narrow searches — broaden the query or add more targets to one run.

Are results de-duplicated?

Yes. Each artifact is emitted once per run, even when it appears on several pages, so you are never billed twice for the same record.

Why are some fields empty?

Maven Central does not publish every attribute for every artifact. Empty means the source did not supply it, not that extraction failed.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two. Raise Max concurrency carefully — the source rate-limits aggressive crawling.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset for time-series analysis.

Does it work behind a proxy?

It uses Apify Proxy automatically. You can switch groups or supply your own proxies in Proxy configuration.

How often does the data change?

Maven Central updates continuously. Re-run whenever you need current data; the Actor always reads the live source, never a cache.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

What if the source changes its format?

Open an issue on the Issues tab and it gets fixed. The Actor is actively maintained.

Is it legal?

This Actor reads only publicly available data from Maven Central — the same content any visitor or client sees without logging in. It does not bypass authentication, does not collect private data and does not attempt to defeat access controls. You are responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved. Scraping public data is generally lawful in the EU and the US, but the responsibility for the downstream use of that data sits with you.

Related scrapers

• npm Package Intelligence — JavaScript registry
• NuGet Scraper — .NET registry
• Packagist Scraper — PHP registry
• Docker Hub Scraper — Container images