Software Cycle Support Declaration Evidence API avatar

Software Cycle Support Declaration Evidence API

Pricing

from $1.00 / 1,000 metadata observations

Go to Apify Store
Software Cycle Support Declaration Evidence API

Software Cycle Support Declaration Evidence API

Track exact endoflife.date product cycles using APIv1 support dates, nullable flags and latest patch declarations. No vendor guarantee, risk score or inferred paid support eligibility.

Pricing

from $1.00 / 1,000 metadata observations

Rating

0.0

(0)

Developer

Salih Can Kurnaz

Salih Can Kurnaz

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

For maintenance planning watchlists, request exact product@cycle records from endoflife.date APIv1. This is a community-maintained third-party source, not the software vendor. Require schema major1 and exact release name; do not infer a cycle from a full installed version or silently use latest. Keep release/LTS dates, active/extended/end-of-life dates and nullable source flags, latest patch name/date. Optional missing extended-support fields remain null rather than false. Preserve YYYY-MM dates at month precision; do not invent a day. No current/future as-of classification, risk score, vulnerability finding, vendor-verified SLA, support entitlement, product description or upgrade recommendation. The selected record does not prove eligibility for paid extended support. Unknown products/cycles and breaking schema changes fail explicitly. Response generation timestamp is recorded in OUTPUT providerCoverage but excluded from semantic row hashes to avoid daily false changes. Original data: endoflife.date contributors, MIT; bundled source notice applies. No third-party pages or latest release links are followed.

Input example

{
"productCycles": [
"python@3.11",
"nodejs@22"
],
"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 an independent validation or entitlement decision.

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. Minimum permitted run budget: $0.0055. Default 256 MB, timeout 120 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 provider request. 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, open-ended 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. Only fixed provider endpoints constructed from validated identifiers are contacted. 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

Original source notice

Copyright 2020 endoflife.date contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.