Maven Central POM Coordinate & License Evidence API

Fetch UTF-8 Maven POM model4.0.0 documents from repo.maven.apache.org for up to five exact group:artifact:version coordinates. Verify artifact identity and the declared group/version, labeling when these come from the immediate parent declaration. Parent POMs are not fetched. Keep local packaging, up to twenty local license name/URL pairs and up to one hundred direct dependency declarations, including literal version expressions and scope. Unresolved ${...} expressions in dependencies are preserved; they are not resolved against properties, a BOM or dependencyManagement. Identity coordinates containing unresolved expressions fail rather than being guessed. Missing local licenses remain null; this is not a claim that the artifact has no license. Missing packaging remains null rather than pretending a declared jar value. Only a published POM is retrieved: no JAR/source archive download, Maven/plugin execution, builds, external schemas or transitive resolution. XML entities/DTDs, non-UTF-8 data, excessive nodes/depth and unexpected namespaces are rejected. Declared license names are not legal clearance, and dependencies are not a compatibility or vulnerability verdict.

Input example

{
  "coordinates": [
    "com.google.guava:guava:33.4.8-jre",
    "org.junit.jupiter:junit-jupiter:5.12.2"
  ],
  "maxResults": 2
}

Outputs and change comparison

One saved observation is one dataset row with itemKey, sourceUrl, contentHash and observedAt. The SHA256 covers only selected semantic fields; retrieval times, API request URLs, download/popularity counters and people are excluded. Copy SNAPSHOT.previousHashes into the next input to compare the same exact watchlist. Statuses are NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. Unchanged observations are still billable. There is no hidden persistent baseline and no missing-row/deletion inference. OUTPUT records actual requestCount, rowsEmitted, source summaries, errors, status and complete. SNAPSHOT.complete is false after any error or when any requested observation could not be delivered. Reaching the selected result cap is PARTIAL_RESULT_CAP; a monetary budget stop is PARTIAL_BUDGET. Provider restrictions produce PARTIAL_PROVIDER_LIMIT. A saved observation means successful metadata extraction only, not that the declared package state is good or safe.

Pricing and bounded work

$0.005 startup plus $0.001 per saved observation, pay per event. Startup quantity follows Apify memory rules with minimum one. Default 256 MB, timeout120 seconds, no restart. Five identifiers and at most five rows; a 55-second fetch deadline and two-MiB decoded-body cap apply. API requests are made only after checking the affordable result capacity. Zero affordable observations causes zero source requests, including no NuGet discovery call. Before each later request and dataset write the budget is checked again. Responses that do not produce a saved row are not charged as observations; startup can still apply. No browser, paid proxy, paid external API or credentials. No network retries, bypasses, API search or bulk pagination. Shared-IP provider limits still apply across runs: avoid parallel requests that exceed provider policy and use supported bulk data channels for large extraction.

Failure and access behavior

Only constructed official HTTPS API endpoints are contacted. Dynamic NuGet resource links must remain within the validated official registration scope. Private addresses and credential-bearing/cross-provider redirects are rejected. HTTP403/429 or Retry-After stops further provider work; successful current responses can be retained. Unknown/missing identifiers are errors, never guessed missing/safe states. All-source failure exits nonzero after preserving OUTPUT; partial delivery preserves successful rows and explicit errors. Source versions and raw declarations can change, and the Actor does not independently verify artifact bytes, publisher identity, signatures or legal rights. Public upstream APIs/data may be free; the fee covers the bounded selection, validation, comparison/output workflow and Apify execution. There is no affiliation, exclusive data access, guaranteed availability, completeness or revenue claim.

Official sources

• https://maven.apache.org/pom.html
• https://repo.maven.apache.org/maven2/