Skip to main content

Endoflife.date

endoflife.date is a community-maintained database that tracks end-of-life (EOL) dates and support lifecycle information for a wide range of software products, including operating systems, programming languages, frameworks, and more. You can bring product data from endoflife.date into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with endoflife.date and how to obtain that information. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select endoflife.date from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to connect endoflife.date with Brinqa:

  • API URL: The base URL for the endoflife.date API. The default setting is https://endoflife.date.
info

The endoflife.date API is publicly accessible and does not require authentication.

Additional settings

The endoflife.date connector contains additional options for specific configuration:

  • Parallel requests: The maximum number of parallel API requests. The default setting is 4.

Types of data to retrieve

The endoflife.date connector can retrieve the following types of data from the endoflife.date API:

Table 1: Data retrieved from endoflife.date

Connector ObjectRequiredMaps to Data Model
ProductYesEOL Advisory
info

The endoflife.date connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from endoflife.date in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

Product

Table 2: Product attribute mappings

Source Field NameSDM Attribute
ProductResource.aliasesALIASES
ProductResource.categoryCATEGORIES
ReleaseResource.codenameCODENAME
ReleaseResource.customCUSTOM
ReleaseResource.discontinuedFromDISCONTINUED_FROM
ReleaseResource.eoasFromEOAS_FROM
ReleaseResource.eolFromEOL_FROM
ReleaseResource.eoesFromEOES_FROM
ReleaseResource.nameCYCLE
ProductResource.identifiersIDENTIFIERS
ProductResource.identifiers (filtered)IDENTIFIER_CPE
ProductResource.identifiers (filtered)IDENTIFIER_PURL
ProductResource.identifiers (filtered)IDENTIFIER_REPOLOGY
ReleaseResource.isDiscontinuedIS_DISCONTINUED
ReleaseResource.isEoasIS_EOAS
ReleaseResource.isEoesIS_EOES
ReleaseResource.isEolIS_EOL
ReleaseResource.isLtsIS_LTS
ReleaseResource.isMaintainedIS_MAINTAINED
ProductResource.labelsLABELS
ProductResource.labels.discontinuedLABEL_DISCONTINUED
ProductResource.labels.eoasLABEL_EOAS
ProductResource.labels.eoesLABEL_EOES
ProductResource.labels.eolLABEL_EOL
ReleaseResource.latest.dateLATEST_VERSION_DATE
ReleaseResource.latest.nameLATEST_VERSION
ProductResource.linksLINKS
ProductResource.links.htmlLINK_HTML
ProductResource.links.iconLINK_ICON
ProductResource.links.releasePolicyLINK_RELEASE_POLICY
ReleaseResource.ltsFromLTS_FROM
ProductResource.nameNAME
ProductResource.labelPRODUCT_LABEL
ReleaseResource.releaseDateRELEASE_DATE
ProductResource.tagsTAGS
Calculated (MD5 hash)UID
ProductResource.versionCommandVERSION_COMMAND

APIs

The endoflife.date connector uses the endoflife.date API. Specifically, it uses the following endpoints:

Table 3: endoflife.date API endpoints

Connector ObjectAPI Endpoint
ProductGET /api/v1/products
GET /api/v1/products/{product}

Changelog

The endoflife.date connector has undergone the following changes:

Table 4: endoflife.date changelog

VersionDescriptionDate Published
3.0.0Initial Integration+ release.January 20th, 2026