API to get multiple product with cycles mapped to them about endoflife.date

[captn3m0]

We have a full product data API in the upcoming v1 of the API: https://deploy-preview-2080--endoflife-date.netlify.app/api/v1/products/full/

Documented at https://deploy-preview-2080--endoflife-date.netlify.app/docs/api/v1/

This might have some stale data, but we're getting closer to taking this live. Feedback is appreciated at #2080.

[welcome]

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

[captn3m0]

While this might be doable, can you provide a use-case for such an API?

[Vasanth2896]

This will be useful for me incase I am maintaining multiple applications such as ansible , Terraform and stackstorm. And having single point of contact with relavant info can help with alerts in case of EOL.

…

On Tue, 28 May 2024, 3:00 pm Nemo, ***@***.***> wrote: While this might be doable, can you provide a use-case for such an API? — Reply to this email directly, view it on GitHub <#5191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMH5C2SAASIZTJRYANNDGL3ZERFELAVCNFSM6AAAAABILBOBRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUG42TQNJRGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nicpenning]

Looking at a SIEM use case where endoflife.date data can be correlated with product information from vulnerability scanners, EDR solutions, and other log sources that live in a central location would be ideal.

I would be interested in an API endpoint that provides all product information with all eol information.

This would allow for SIEM queries to match on endoflife products and alert security analysts or visualize via dashboards what software is end of life in the environment. This would be another source of this as vulnerability scanners do contain some of this information but this would further validate or identify others.

The current API endpoints are too limiting to simply ingest them as a source for collation in a SIEM. Having just 1 API call to have all of the data that can be checked against every 24 hours (or as needed) would make this an easy source for correlation. Otherwise, more advanced queries are needed to target the product, then get the details for that product. Currently the body details of the request also do not contain the product itself which might be another FR on it's own if an endpoint does not provide all details for all products to something like this (Ubuntu example):

[
  {
    "cycle": "21.04",
    "lts": false,
    "releaseDate": "2021-04-22",
    "support": "2022-01-01",
    "eol": "2022-01-01",
    "latest": "21.04",
    "link": "https://wiki.ubuntu.com/HirsuteHippo/ReleaseNotes/",
    "product" : "ubuntu"
  },
  {
    "cycle": "20.10",
    "lts": false,
    "releaseDate": "2020-10-22",
    "support": "2021-07-07",
    "eol": "2021-07-07",
    "latest": "20.10",
    "link": "https://wiki.ubuntu.com/GroovyGorilla/ReleaseNotes/",
    "product" : "ubuntu"
  }
]

[captn3m0]

Would a Prometheus exporter work for you?

#975

[nicpenning]

Not for me it seems. I am looking for direct and simple APIs to reveal this info.