Maven Central Scraper — Java Artifact Metadata & Versions

Extract comprehensive metadata from Maven Central, the canonical repository for Java libraries and JVM artifacts. This Actor returns groupId, artifactId, latest version, packaging type, version counts, and complete version history for any Java package you need to track. Whether you are auditing a dependency supply chain, monitoring third-party libraries, or building a catalog of the Java ecosystem, this tool delivers structured data without writing a single line of Java.

Use Cases

• Dependency auditing — Pull metadata and version history for every library in your build.
• Supply-chain research — Track which versions of a library are published and when they were last updated.
• Java ecosystem mapping — Build searchable catalogs of artifacts with groupId, artifactId, and version data.
• Competitive analysis — Compare release cadence and popularity across JVM libraries.
• License and compliance checks — Gather artifact coordinates and version ranges for SBOM generation.
• Release monitoring — Watch for new versions of critical dependencies like Spring, Guava, or Jackson.

Input

Output

The Actor outputs a dataset with one row per artifact:

{
  "groupId": "com.google.guava",
  "artifactId": "guava",
  "latestVersion": "33.4.8-jre",
  "packaging": "bundle",
  "versionCount": 150,
  "timestamp": "2025-04-14T18:45:22.422Z",
  "versions": "33.4.8-jre, 33.4.8-android, 33.4.7-jre, ...",
  "sourceUrl": "https://central.sonatype.com/artifact/com.google.guava/guava",
  "error": ""
}

Pricing

Pay per event: $0.001 per artifact extracted.

Limitations

• Maven Central search results are limited to what the public Solr API returns.
• Very large version histories may be truncated to the API maximum.
• Version history requires one additional API call per artifact.

FAQ

Q: Can I search by exact coordinates? A: Yes. Set both groupId and artifactId for an exact lookup, or use groupId alone to list artifacts in a group.

Q: What if a search query returns many artifacts? A: Use maxItems to limit the total number of results returned.

Changelog

• v1.0.0 — Initial release.