ReleaseRun Badges for Terraform

Why Use Terraform Health Badges?

Terraform moves fast, and provider compatibility breaks quietly. A health badge in your module README or infrastructure documentation shows whether your Terraform version is still actively supported, so your team does not discover version issues mid-deployment.

ReleaseRun badges go beyond Shields.io. While Shields.io shows a version number, our badges show security posture: CVE counts, EOL countdowns, and a composite health grade that factors in freshness (35%), security (35%), and support status (30%).

Terraform Release History & EOL Timeline

HashiCorp generally maintains the current and one prior minor version of Terraform. With the shift to the BSL license in August 2023 and the emergence of OpenTofu as a community fork, tracking which versions are actively maintained has become more important than ever.

• Terraform 1.10 – released late 2024. Current stable release. Actively maintained with bug fixes and security patches.
• Terraform 1.9 – released mid-2024. Still receiving critical patches as the previous minor release, but will lose support once 1.11 ships.
• Terraform 1.8 – released early 2024. No longer actively maintained. Security patches may still land for critical issues, but routine fixes have stopped.
• Terraform 1.7 – released January 2024. Introduced the removed block and provider-defined functions. No longer receiving updates.
• Terraform 1.6 – released October 2023. Added the terraform test command. Unsupported.
• Terraform 1.5 – released June 2023. The last version released under the MPL license before the BSL switch. Some organizations pinned to this version to avoid the license change. No longer receiving patches.

The rapid minor-release cadence (roughly every 3-4 months) means older versions fall out of support quickly. Health badges help module authors and platform teams communicate version requirements clearly.

Badge Customization Examples

ReleaseRun offers four badge types for Terraform. Each serves a different monitoring purpose:

• Health badge – composite A-F grade reflecting overall risk. Embed: ![Terraform Health](https://img.releaserun.com/badge/health/terraform.svg)
• EOL badge – end-of-life or support status. Embed: ![Terraform EOL](https://img.releaserun.com/badge/eol/terraform.svg)
• Version badge – latest stable version number. Embed: ![Terraform Version](https://img.releaserun.com/badge/v/terraform.svg)
• CVE badge – known vulnerability count. Embed: ![Terraform CVE](https://img.releaserun.com/badge/cve/terraform.svg)

Add ?style=flat-square or ?style=for-the-badge to any URL for alternative rendering. The embed builder above lets you preview all styles before copying.

Common Use Cases

• Module authors: Specify which Terraform versions your module is tested against and show their health status. When a version loses support, the badge automatically updates so consumers know to pin to a newer version.
• Platform engineering teams: Track Terraform versions across multiple teams and workspaces. In large organizations, different teams often run different Terraform versions. Badges in a central wiki or portal highlight which teams are falling behind.
• CI/CD pipelines: Add a Terraform health badge to your pipeline status page. If the Terraform binary in your CI runner goes stale, the badge provides a visual cue before a breaking provider update forces an emergency upgrade.
• OpenTofu migration tracking: If your team is evaluating OpenTofu alongside Terraform, badges for both help compare support timelines and make an informed decision about which to standardize on.

Related ReleaseRun Tools

Terraform badges are part of a broader toolkit for managing your infrastructure-as-code lifecycle:

• Terraform Version Checker – scan your .tf files and state to identify which Terraform and provider versions you are running.
• Tech Stack Health Scorecard – get a holistic health grade across your entire infrastructure stack, not just Terraform.
• Upgrade Path Planner – plan your migration from Terraform 1.5 to 1.10 with provider compatibility checks and state migration guidance.
• Config Drift Detector – identify differences between your Terraform state and the actual cloud resources to catch manual changes.
• Badge Generator – create custom health badges for any product in the ReleaseRun database.

What Makes These Different

Every badge pulls live data from the endoflife.date API and the NIST National Vulnerability Database. Data refreshes every 6 hours. Badges are edge-cached for 5 minutes, fast enough for CI pipelines, Terraform Registry module pages, and internal documentation portals.