argoproj/argo-events

Event-driven Automation Framework for Kubernetes

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

argoproj/argo-events has 2.5k+ stars and 800+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 58 minutes ago
Added to GitGenius on August 31st, 2021
Created on May 17th, 2018
Open Issues & Pull Requests: 156 (+0)
GitHub issues: Enabled
Number of forks: 841
Total Stargazers: 2,705 (+0)
Total Subscribers: 32 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 61.2 days
Mean response time: 309.3 days
90th percentile: 967.9 days
Tracked items: 189

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 2 weeks, while "enhancement" waits about 13 months. 62% of issues opened in the past year have been closed, leaving a working backlog. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 145
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 1,089 days
Stale 30+ days: 138
Stale 90+ days: 136

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (448)
  • bug (444)
  • stale (161)
  • good first issue (28)
  • pinned (26)
  • help wanted (22)
  • security (15)
  • documentation (12)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Argo Events is an event-driven workflow automation framework designed specifically for Kubernetes environments.

The core functionality of Argo Events centers on connecting event sources to sensors that define business logic and trigger actions. The framework is CloudEvents compliant, ensuring compatibility with standardized event formats across cloud-native ecosystems. Users can manage automation scenarios ranging from simple linear real-time events to complex multi-source event orchestration, with the ability to customize business-level constraint logic for their specific workflow automation needs. The project provides comprehensive documentation covering concepts, quick-start guides, event source and sensor deployment instructions, and linting tools for EventSource and Sensor resources.

The repository maintains active development with significant community engagement.

Argo Events integrates closely within the broader Argo project ecosystem. This interconnection allows users to build comprehensive automation pipelines combining event-driven triggers with workflow execution and continuous deployment capabilities.

The project is governed by the CNCF Code of Conduct and is licensed under Apache License Version 2.0. A demo environment is available for users to explore Argo Events functionality through GitHub authentication. The framework has been adopted by organizations including BlackRock, as evidenced by public presentations on automating research workflows. The project maintains an official user list documenting organizations leveraging Argo Events in production environments, and contributions are actively encouraged through documented contributing guidelines and a dedicated security policy.