May’d It

DATA TOOLS / ai

Software Lifecycle Watchlist Monitor

Monitor exact software release cycles, published support deadlines and saved date revisions. Export lifecycle evidence for upgrade planning without scanning systems or inferring compliance.

JSON / CSV outputLimited permissionsSource: maydit/software-lifecycle-watchlist-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

Keep an exact list of software release cycles and their published support deadlines. Export community-maintained endoflife.date declarations, calculated UTC deadline windows and saved date revisions for an upgrade-planning queue.

observationIdproductLabelcycleendOfLifeDatedaysToEndOfLifedeadlineWindow

Try a small watchlist

Paste this exact input into Console's JSON editor. No source API key is required. These historical examples demonstrate the fields; they are not recommendations to install these versions.

{
  "watchlist": [
    {
      "product": "nodejs",
      "cycle": "22"
    },
    {
      "product": "python",
      "cycle": "3.10"
    }
  ],
  "maxResults": 5
}

Open Dataset for saved observations and Run report for coverage. SUMMARY is the machine-readable record. Empty API input and the Console prefill use the documented sample inventory; the maximum is a cap, not a promised result count.

Check the fit and source limits
  • Exact inventory: up to 50 product/cycle entries. No URL crawling, patch-version inference, installed inventory scan or all-product enumeration. Missing cycles fail explicitly; they never become fictitious lifecycle rows.
  • Source scope: endoflife.date is community-maintained and its API is documented as beta. Verify important dates with the linked vendor policy; extended-support dates do not imply you have a paid support entitlement.
  • Date meaning: all displayed date-only values are source dates. Countdown windows use the observation's UTC date. Unknown dates remain null; source flags remain separate and may use product-specific labels.
  • Useful corrections: only source observation fields trigger saved changes. Daily countdowns remain available in ordinary repeated rows.
  • Access and budgets: public documented APIs only, sequential requests, pinned public DNS and no cross-host redirect following. Responses are capped at 2 MiB. One bounded retry is allowed for 502/503/504; rate/access refusals are reported without bypass.
  • Run bounds: maxRunSeconds defaults to 240 and also respects the platform deadline minus 25 seconds. Configure Apify's maximum total charge as well as maxResults.

SUMMARY includes saved/observed counts, per-source coverage, unreached entries, history outcome and time/spending limits. Intentional output caps are bounded samples. Source, source-window, time and history failures are partial or failed. All-source or all-output failures fail the run. Errors and no-match diagnostics are never paid data rows.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-10-18. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "observationId": "nodejs:20",
  "productLabel": "Node.js",
  "cycle": "20",
  "endOfLifeDate": "2026-04-30",
  "daysToEndOfLife": -171,
  "deadlineWindow": "past",
  "activeSupportEnds": "2024-10-22",
  "extendedSupportEnds": null,
  "isMaintained": true,
  "sourceUrl": "https://endoflife.date/api/v1/products/nodejs/",
  "observedAt": "2026-10-18T13:04:38.943Z"
}

Historical output from this run; the current example input is a separate starting configuration and may produce different records. Run reference: UiWVXBHwHwZONOTdg. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

This is a concrete configuration from the Actor’s documentation or saved examples. Adjust its targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "watchlist": [
    {
      "product": "nodejs",
      "cycle": "22"
    },
    {
      "product": "python",
      "cycle": "3.10"
    }
  ],
  "maxResults": 5
}
Download input.json

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
watchlistarray

Up to 50 objects with exact product and cycle strings. Product slugs and cycle names come from endoflife.date. Omitted or empty uses Node.js 22, Python 3.10 and Ubuntu 22.04. Patch versions, URLs and automatic installed-version discovery are not supported.

maxResultsinteger

Caps confirmed dataset rows, including saved unchanged observations. A limit is a sample, not a complete inventory; inspect sourceCoverage and sourcesNotReached in SUMMARY.

comparePreviousboolean

First observations are new. Later rows include changed/unchanged status, prior saved values and changedFields. Only confirmed saved rows advance history.

onlyChangesboolean

Implies comparison. Rolling countdowns and deadline windows do not trigger changes. Leave false to export daily approaching-deadline observations.

snapshotNamestring

1-80 letters, numbers, underscores or hyphens. History also includes the exact sorted inventory. Use one writer per scope; changing the inventory starts a separate baseline.

stateStoreNamestring

3-63 letters, numbers or hyphens. Accessed only for comparisons. Use a dedicated store for each customer workflow.

maxRunSecondsinteger

Includes source and comparison work; also bounded by the platform deadline minus 25 seconds. Each response is capped to 2 MiB. Access and rate refusals are reported.

Output fields

observationIdproductLabelcycleendOfLifeDatedaysToEndOfLifedeadlineWindowactiveSupportEndsextendedSupportEndsisMaintainedcomparisonStatuschangedFieldsendOfLifeDateShiftDaysvendorPolicyUrlsourceUrlobservedAt

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Software lifecycle observation$0.002One software lifecycle observation saved to the dataset. Failed source requests do not produce paid rows.

Check current Apify pricing ↗ before running.

Use with an AI agent or API

Connect this Actor through MCP

Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the official configurator provides client-specific instructions.

{
  "mcpServers": {
    "maydit": {
      "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/software-lifecycle-watchlist-monitor"
    }
  }
}

Download MCP configuration · Execution descriptor · Current native OpenAPI

Ask the agent to inspect maydit/software-lifecycle-watchlist-monitor (Actor ID qqPduGtKLZi4Ylu6b) with fetch-actor-details, including input, output and pricing. Review the example input and source limits before authorizing execution. For call-actor, place a maximum charge of $0.05 and timeout of 300 seconds in callOptions, not the Actor input. A spending cap can stop a run before its intended scope completes.

After starting once, keep the returned run ID. Use get-actor-run for status, get-key-value-store-record for that run's SUMMARY, and get-dataset-items with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.

Supply your own credentials

For direct API use, set APIFY_TOKEN securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.

This input schema has no source-credential fields. Apify authorization is still required to start a paid run.

Start once, then retrieve the same run

Download run-actor.mjs, execution.json and input.json into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.

# Preview only: makes no requests
node run-actor.mjs

# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run

# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run

The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.

It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.

Review run-status.json, summary.json, items.json and download-receipt.json. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.

For a custom integration, use the same sequence:

  1. POST https://api.apify.com/v2/actors/qqPduGtKLZi4Ylu6b/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS with a JSON input body and Bearer authorization. Save data.id once.
  2. GET https://api.apify.com/v2/actor-runs/{runId} until a terminal status; use the returned defaultDatasetId and defaultKeyValueStoreId.
  3. GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY; interpret diagnostics using this Actor's coverage guide.
  4. GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100; paginate the same completed dataset and retain source URLs/timestamps.

The official run API, dataset pagination documentation and MCP guide describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.2. Example outputs retain their original sample context; they are not live results.

Software Lifecycle Watchlist Monitor — illustrative watchlist workflow

Turn release support dates into a reviewable inventory

Keep an exact list of software release cycles and their published support deadlines. Export community-maintained endoflife.date declarations, calculated UTC deadline windows and saved date revisions for an upgrade-planning queue.

One result is one product/release-cycle observation. The Actor does not inspect systems or discover installed versions. Source declarations remain separate from calculated countdowns.

First run · Output preview · Saved comparisons · Pricing

Try a small watchlist

Paste this exact input into Console's JSON editor. No source API key is required. These historical examples demonstrate the fields; they are not recommendations to install these versions.

{
  "watchlist": [
    {
      "product": "nodejs",
      "cycle": "22"
    },
    {
      "product": "python",
      "cycle": "3.10"
    }
  ],
  "maxResults": 5
}

Open Dataset for saved observations and Run report for coverage. SUMMARY is the machine-readable record. Empty API input and the Console prefill use the documented sample inventory; the maximum is a cap, not a promised result count.

Output preview

Planning question Fields Interpretation
Which release? observationId, product, cycle Exact requested inventory identity
What deadlines are published? activeSupportEnds, endOfLifeDate, extendedSupportEnds, labels Distinct source support phases; null means no date was supplied
Is it approaching a deadline? asOfDate, daysToEndOfLife, deadlineWindow UTC date calculation, not a vendor promise or risk score
What does the source report? isEoas, isEol, isEoes, isMaintained, isLts Nullable source flags, not inferred from missing dates
Did the deadline move? endOfLifeDateShiftDays, activeSupportDateShiftDays Positive means the saved date moved later; null means no two dated observations
Where is the evidence? vendorPolicyUrl, sourceUrl, sourceLastModifiedAt, observedAt Vendor policy link, community source and retrieval time

Latest release metadata is available in latest. The snapshot includes source dates, flags, labels and latest release metadata. daysToEndOfLife, deadlineWindow, observation time and source generation timestamps are excluded from comparisons: the passage of one day alone does not create a source-change event. Use onlyChanges: false and filter the deadline fields downstream for approaching-deadline reminders.

Inspect a second inventory

Inspect Ubuntu 22.04 and 24.04 support declarations with distinct standard and extended-support dates.

{
  "watchlist": [
    {
      "product": "ubuntu",
      "cycle": "22.04"
    },
    {
      "product": "ubuntu",
      "cycle": "24.04"
    }
  ],
  "maxResults": 5
}

Save a comparison baseline

Record Node.js 22 once, then compare future published support dates and latest-release metadata against saved values.

{
  "watchlist": [
    {
      "product": "nodejs",
      "cycle": "22"
    }
  ],
  "comparePrevious": true,
  "snapshotName": "node22-lifecycle-review",
  "maxResults": 5
}
  1. Run once to save new observations.
  2. Repeat with the same inventory, snapshotName and named history store. Rows become changed or unchanged, with previous, previousObservedAt and changedFields.
  3. Add onlyChanges: true to suppress unchanged source observations. This also enables comparison. A healthy repeat can save zero rows.
  4. In Sheets, Make or n8n, wait for completion, check SUMMARY, then upsert by observationId. Keep the run ID for replay and deduplicate deliveries with observationId + contentHash.

The versioned history scope contains the exact sorted inventory and namespace. Changing that inventory starts a separate comparison. Only confirmed dataset writes advance history. Errors, unsaved capped rows and unchanged skips preserve prior observations; missing sources never imply deletion. Use one writer per scope: a pre-commit check detects existing concurrent changes, but is not an atomic lock. The named store holds at most 20,000 saved identities per scope.

The Actor supplies observations and a report. You configure schedules, alerts and downstream accounts. A history failure can leave valid saved rows; inspect historyUpdated and failedSources.history. Comparisons cover last saved observations, not every upstream change between runs.

Coverage and interpretation

  • Exact inventory: up to 50 product/cycle entries. No URL crawling, patch-version inference, installed inventory scan or all-product enumeration. Missing cycles fail explicitly; they never become fictitious lifecycle rows.
  • Source scope: endoflife.date is community-maintained and its API is documented as beta. Verify important dates with the linked vendor policy; extended-support dates do not imply you have a paid support entitlement.
  • Date meaning: all displayed date-only values are source dates. Countdown windows use the observation's UTC date. Unknown dates remain null; source flags remain separate and may use product-specific labels.
  • Useful corrections: only source observation fields trigger saved changes. Daily countdowns remain available in ordinary repeated rows.
  • Access and budgets: public documented APIs only, sequential requests, pinned public DNS and no cross-host redirect following. Responses are capped at 2 MiB. One bounded retry is allowed for 502/503/504; rate/access refusals are reported without bypass.
  • Run bounds: maxRunSeconds defaults to 240 and also respects the platform deadline minus 25 seconds. Configure Apify's maximum total charge as well as maxResults.

SUMMARY includes saved/observed counts, per-source coverage, unreached entries, history outcome and time/spending limits. Intentional output caps are bounded samples. Source, source-window, time and history failures are partial or failed. All-source or all-output failures fail the run. Errors and no-match diagnostics are never paid data rows.

Pricing

Base FREE-tier rate: $2 per 1,000 saved observations, plus the listed Actor Start charge. The Pricing tab is authoritative for your plan. Saved unchanged observations are billable; unchanged rows suppressed by onlyChanges have no dataset-item charge. Platform and storage charges may apply under your plan.

Sources and support

API v1 documentation · Project and API status · MIT license

Lifecycle data is attributed to endoflife.date contributors. The source license notice is included in LICENSE-SOURCES.txt. Product descriptions and third-party logos are not copied. This community Actor is not affiliated with endoflife.date or the software vendors.

For help, open Issues with the run URL and expected public field, or contact bmay@mayd-it.com. Remove credentials and private inventory information before posting.