# StackStorm/st2 — Open-Source Technical Health & Evaluation Audit

> **GitiGit Verified Evaluation** | Analyzed on 2026-09-24 | Canonical URL: https://gitigit.dev/repository/stackstorm-st2

## Executive Summary
- **Repository:** `StackStorm/st2`
- **Primary Language:** Python
- **Community Adoption:** 6,538 stars · 788 forks
- **License:** Apache License 2.0 (OSI-compliant)
- **Quality Score:** **90/100** (Grade: **A+**)
- **Production Readiness Verdict:** **Production Grade**

## Technical & Maintainer Health Telemetry
- **Commit Cadence:** Active continuous commits verified across 52-week rolling window.
- **Security Posture:** 0 critical unpatched CVE advisories detected in public vulnerability registries.
- **Dependency Health:** Automated dependency update workflows configured and operational.
- **Architecture Posture:** Modular structure with automated continuous integration (CI) testing suites.

## Context & Best Use Cases
StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html

- **When to Choose:** Ideal when your architecture requires a high-performance Python solution with active community support.
- **When to Consider Alternatives:** In enterprise environments requiring formal commercial SLAs or strict specialized compliance guarantees.

## Data Provenance & Methodology
- **Source of Truth:** Verified GitHub API git history, release logs, and NVD CVE vulnerability records.
- **Zero Fabrication Guarantee:** All scores are computed deterministically from observed static repository facts.
- **Methodology Reference:** https://gitigit.dev/methodology
- **Interactive Profile:** https://gitigit.dev/repository/stackstorm-st2
- **Compare Alternatives:** https://gitigit.dev/alternatives/stackstorm-st2