# Software Lifecycle Watchlist Monitor — workflow

## Choose this tool

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.

Useful output columns: `observationId`, `productLabel`, `cycle`, `endOfLifeDate`, `daysToEndOfLife`, `deadlineWindow`.

## Practical workflow

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.

```json
{
  "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

- **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.

## Real output sample

One selected row from a 2026-10-18 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: UiWVXBHwHwZONOTdg. Summary status: ok. Incomplete: false.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "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"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [OSV Package Advisory Monitor](https://mayd-it.com/data-tools/actors/osv-package-advisory-monitor/)

Check explicit package ecosystem/name/version identities for known advisories; do not substitute a release or container tag for a package version.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Package registries, container tags, support lifecycles and vulnerability advisories have different identifiers. Verify ecosystem, package, exact version and source scope before matching records.

### [Vendor Incident Monitor - Public Outage Feeds](https://mayd-it.com/data-tools/actors/vendor-incident-feed-monitor/)

Keep public vendor incident notices in a separate operational timeline when diagnosing whether an observed change affects your own workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Package registries, container tags, support lifecycles and vulnerability advisories have different identifiers. Verify ecosystem, package, exact version and source scope before matching records.
