JVM Artifact Release Monitor
Pricing
$2.00 / 1,000 checked jvm artifacts
JVM Artifact Release Monitor
Monitor explicit public JVM artifact coordinates for newly published releases with bounded Maven Central REST lookups and change-only dataset output.
Pricing
$2.00 / 1,000 checked jvm artifacts
Rating
0.0
(0)
Developer
Marcel K
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
24 days ago
Last modified
Categories
Share
Monitor an explicit watchlist of public JVM artifact coordinates for newly published releases. The Actor uses the Maven Central REST search endpoint, persists a small baseline per coordinate, and returns only changed release records by default.
What it does
- Accepts explicit
groupId+artifactIdpairs only; it does not discover packages or scrape maintainers. - Makes one bounded public REST query per unique coordinate.
- Records the latest version, packaging, publication timestamp when provided, and available file extensions.
- Persists a normalized source snapshot by
baselineKeyto detectavailability,latest_version, andrelease_metadatachanges. - Returns structured per-artifact error rows instead of failing an entire watchlist run.
- Omits unchanged records by default to keep scheduled datasets compact.
Good use cases
- Java/JVM platform teams maintaining a focused dependency watchlist.
- DevOps teams that need a lightweight release-change feed for specific artifacts.
- Security and engineering teams collecting source evidence before their own upgrade review process.
Input
artifacts: required list of{ "groupId", "artifactId" }objects.maxArtifacts: run cap from 1 to 25; v1 defaults to 10.includeUnchanged: include unchanged source records after an initial baseline.baselineKey: separate stored baselines for environments, clients, or schedules.
Example:
{"artifacts": [{ "groupId": "org.apache.logging.log4j", "artifactId": "log4j-core" }],"maxArtifacts": 10,"includeUnchanged": false,"baselineKey": "production"}
Output
Each dataset item is a changed, explicitly included unchanged, or errored coordinate.
{"coordinate": "org.apache.logging.log4j:log4j-core","groupId": "org.apache.logging.log4j","artifactId": "log4j-core","checkedAt": "2026-07-10T00:15:00.000Z","status": "ok","changed": true,"changeTypes": ["latest_version"],"latestRelease": {"version": "2.26.0","packaging": "jar","publishedAt": "2026-04-01T00:00:00.000Z","extensions": [".jar", ".pom"]},"previousLatestRelease": { "version": "2.25.4" },"sourceUrl": "https://search.maven.org/solrsearch/select?...","snapshotHash": "...","warnings": []}
status values:
ok: Maven Central returned a latest release record.not_found: Maven Central returned no release record for that coordinate.error: invalid coordinate or a source failure; inspectwarningsfor a machine-readable code.
Pricing status
Pay Per Event is enabled at $0.002 per checked JVM artifact using the checked-jvm-artifact event. Input is capped at 25 artifacts, so a full run costs at most $0.05 in event charges. Charging happens before each Maven Central source request and stops before the next source request when the Apify event-charge limit is reached.
Source, terms, and limitations
- Source: Maven Central REST Search API, documented for JSON access from non-browser user agents: https://central.sonatype.org/search/rest-api-guide/.
- Public source records only. No login, cookies, browser automation, proxy, private repository, private network, user data, or maintainer/lead enrichment.
- A source result does not establish dependency compatibility, licensing, vulnerability status, update safety, or an upgrade recommendation.
- Maven Central may delay, change, or omit metadata. The Actor reports the source record it sees and should be used as monitoring evidence, not as the sole deployment gate.
- This is an unofficial independent tool and is not affiliated with, endorsed by, or sponsored by Apache Maven, Maven Central, or Sonatype. All third-party names belong to their respective owners. No third-party logos or branded assets are used.
Recommended workflow
- Run once with a stable
baselineKeyto establish a baseline. - Schedule future checks with the same key.
- Keep
includeUnchanged=falsefor a compact change-only feed. - Use
includeUnchanged=truewhen an audit trail of all checks is required. - Feed changed records into your own review process; do not automate upgrades from this data alone.