Apache Groovy Lifecycle policy

Apache Groovy is tracked by BlackTree as a programming language implementation or runtime. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Main capabilities

Application and script execution
Standard language tooling and libraries
Versioned compatibility and security maintenance

Typical use

Used to develop and execute software, automation and data-processing workloads.

Deployment

Installed as a runtime, development toolchain, application dependency or managed platform component.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	Apache Groovy
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 1 Oct 2026

These 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 28 Sep 2026

OSV 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

Apache Groovy official lifecycle source

Here we indicate a former major version's bugfix release. | How long is a major version maintained? | That depends on the users. Let's say we have X in maintenance and Y is the official major version, then if a new major version Z is released, Y goes into maintenance. Usually we make one or two more bugfix releases for X and then we discontinue it, unless there are strong requests to have certain things fixed for users that can absolutely not upgrade. | Groovy | Learn

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 28 Sep 2026 · Review state accepted

Open official vendor source