falcosecurity/falcosidekick

Connect Falco to your ecosystem

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

falcosecurity/falcosidekick has 650+ stars and 200+ forks on GitHub, is written in Go, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 3 minutes ago
Added to GitGenius on October 15th, 2026
Created on September 14th, 2018
Open Issues & Pull Requests: 24 (+0)
GitHub issues: Enabled
Number of forks: 231
Total Stargazers: 696 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 42.2 hours
Mean response time: 34.4 days
90th percentile: 90.2 days
Tracked items: 59

How this project is maintained

Work labelled "kind/bug" is answered fastest, typically in about 8 hours, while "kind/feature" waits about 2 days. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 205 days
Stale 30+ days: 3
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 5

Top labels

  • kind/bug (29)
  • kind/feature (23)
  • lifecycle/rotten (22)
  • kind/documentation (5)
  • help wanted (2)
  • lifecycle/stale (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Falcosidekick is a daemon that connects Falco security events to your ecosystem by forwarding them to multiple outputs in a fan-out pattern.

The tool solves the problem of integrating Falco's runtime security alerts with downstream systems. Falco detects suspicious behavior in containers and Kubernetes environments, but its output needs to reach various platforms for alerting, logging, and response. Falcosidekick acts as a single endpoint that accepts Falco events and distributes them to multiple destinations simultaneously, allowing many Falco instances to feed into one daemon rather than requiring direct connections from each instance to each output system.

Teams running Falco in containerized or Kubernetes environments should adopt this tool if they need to route security events to chat platforms, monitoring systems, log aggregators, object storage, serverless functions, message queues, email, databases, SIEM systems, or workflow automation tools. The project supports a broad range of outputs across these categories, making it suitable for organizations with heterogeneous tooling. It works equally well for small deployments with a few Falco instances and large setups with many sources feeding into centralized event processing.

The project maintains steady development activity with regular commits and releases. The codebase is written in Go and includes comprehensive test coverage. The tool provides multiple metrics and observability options including Prometheus metrics, StatsD/DogStatsD integration, and Golang ExpVar for monitoring its own performance. Configuration is handled through YAML files, and the project supports deployment across multiple environments including Docker, systemd, and Kubernetes with Helm charts. Mutual TLS support is available for secure communication between Falco instances and the daemon.