Product overview
KEDA is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.
Main capabilities
- Networked or application service delivery
- Administrative and operational interfaces
- Versioned maintenance and security updates
Typical use
Used to provide application, infrastructure or operational services to other systems and users.
Deployment
Deployed on servers, virtual machines, containers or managed infrastructure.
This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page ↗.
Collected lifecycle data
| Product | KEDA |
|---|
| Release | Lifecycle policy |
|---|
| Start or release | Not extracted |
|---|
| Lifecycle boundary | Continuous or not dated in the source |
|---|
| Date precision | Unknown |
|---|
Known exploited vulnerabilities
Catalogue updated 28 Sep 2026These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.
No CISA known-exploited entries currently match this mapped product family.
This does not mean the product has no vulnerabilities.
Package vulnerability advisories
Checked 26 Sep 2026OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.
No package advisories have been linked for this product identity.
This is not evidence that the product has no vulnerabilities.
Source evidence
PRIMARYManual
KEDA official lifecycle source
If you want to be notified of new releases, we recommend watching our KEDA Core repository on GitHub and ensure you are subscribing for releases. | Next to that, you can join the conversation for every new release on GitHub Discussions . | Removing Features, Breaking Changes & Deprecations | Every new major version, KEDA maintainers are allowed to remove features or make breaking changes as per semantic versioning . | Along with such a release there will always be a migration guide to provide an overview of what has changed, what the impact is and how to migrate. Here is an example of our v1.x to v2.0 migration guide ( example ). | For every one of these, KEDA will always announce a deprecation notice on GitHub Discussions that provides context on why it is changing, what the impact is, when it will change and what steps that are required to be taken. | In majority of the cases, we will allow you to already migrate in the next minor version where we introduce the deprecation so that you can migrate fast.
Publisher identity used by product-specific official-source collectors.
First collected 12 Sep 2026 · Last collected 22 Sep 2026 · Review state accepted
Open official vendor source ↗