Skip to content
CAI
Produce a survey ↗Verify a survey

jpsuldo1/st2

This system is an enterprise-grade automation platform that orchestrates and executes distributed actions across Linux, Windows, and cloud environments. It provides a unified interface for managing workflows, sensors, and rules, supported by a comprehensive CLI and REST API. The architecture emphasizes modularity, security through RBAC, and extensibility via a pack-based content model.

38.1

Weak · 5 August 2026

54k

lines of production code

Python

primary language

2

bus factor · 93 authors in all

2

measurements over time

CAI band scale
CAI trend line

How it got here

2014 · modularization and CLI development

This period focused on modularizing the codebase by splitting monolithic modules into smaller, focused components and establishing a robust build and packaging infrastructure for all packages. Significant work was also dedicated to the st2client, introducing a new command-line interface with structured output formatting and comprehensive model mapping.

93 changes

2015 · RBAC, garbage collection, and exporter

This period focused on introducing role-based access control, automated data purging, and execution export capabilities. The team also added a debug information submission tool, expanded the Linux and ChatOps packs, and established a robust CI/CD pipeline for automated testing.

56 changes

2016–2017 · runner expansion and infrastructure modernization

This period focused on significantly expanding the platform's execution capabilities by introducing new action runners for remote, Windows, and workflow orchestration, alongside a major refactoring of the streaming and CI infrastructure. The team also standardized testing and linting configurations while adding comprehensive test coverage for the new components.

44 changes

CAI lens gauges

Survey your own repository

jpsuldo1/st2 was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.

Survey a repository

About this page

  • The description of this project is derived from its own commit history, not from its README.
  • The score is its highest published measurement, taken on 5 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 1527076de1 — the exact code this score is about.
  • Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.
CAI link cards