[GH-ISSUE #1752] Integration of endoflife.date in the software list #3033

New issue

Open

opened 2026-03-14 06:17:59 +03:00 by kerem · 3 comments

kerem commented

2026-03-14 06:17:59 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Feb 7, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1752

Is your feature request related to a problem? Please describe.
Something that would help with software management would be to integrate https://endoflife.date/docs/api in the software list of each installed agent.

Describe the solution you'd like
a simple badge with the current status returned by the api of endoflife after each software.
this also could be added after the current OS installed to have an easy way of seeing the status of support for each agent.

Describe alternatives you've considered
i didnt find any alternative.
the next best thing would be scripting it but it look like something that could be natively supported by the rmm as the information is already there and would add a lot of value to TRMM.

Additional context

Originally created by @P6g9YHK6 on GitHub (Feb 7, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1752 **Is your feature request related to a problem? Please describe.** Something that would help with software management would be to integrate https://endoflife.date/docs/api in the software list of each installed agent. **Describe the solution you'd like** a simple badge with the current status returned by the api of endoflife after each software. this also could be added after the current OS installed to have an easy way of seeing the status of support for each agent. **Describe alternatives you've considered** i didnt find any alternative. the next best thing would be scripting it but it look like something that could be natively supported by the rmm as the information is already there and would add a lot of value to TRMM. **Additional context** ![image](https://github.com/amidaware/tacticalrmm/assets/17877371/fedd0fed-a76d-4bae-8686-31ca4f53f6e6)

kerem commented

2026-03-14 06:18:05 +03:00

Author

Owner

@bbrendon commented on GitHub (Feb 22, 2024):

At first glance, I don't see how you could match the Installed Software Name with the API which makes this seem impossible.

@bbrendon commented on GitHub (Feb 22, 2024): At first glance, I don't see how you could match the Installed Software Name with the API which makes this seem impossible.

kerem commented

2026-03-14 06:18:10 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Feb 24, 2024):

At first glance, I don't see how you could match the Installed Software Name with the API which makes this seem impossible.

you are right the matching is an issue this proposal would probably require a little bit of legwork to create a matching entry database.
An initial collaborative effort could be levraged to build this list.

or it's not worth and the idea not viable and this is why nobody has this features anywhere.

@P6g9YHK6 commented on GitHub (Feb 24, 2024): > At first glance, I don't see how you could match the Installed Software Name with the API which makes this seem impossible. you are right the matching is an issue this proposal would probably require a little bit of legwork to create a matching entry database. An initial collaborative effort could be levraged to build this list. or it's not worth and the idea not viable and this is why nobody has this features anywhere.

kerem commented

2026-03-14 06:18:16 +03:00

Author

Owner

@dinger1986 commented on GitHub (Mar 10, 2024):

by the time a matching entry database has been built you might as well build out EOL software database as well, its a huge ask

@dinger1986 commented on GitHub (Mar 10, 2024): by the time a matching entry database has been built you might as well build out EOL software database as well, its a huge ask