raystack/raccoon
Raccoon is an event ingestion service that collects, serializes, and routes events to various backend sinks such as Kafka, Kinesis, and Pub/Sub. It provides a structured Go-based architecture with a command-line interface and supports multiple transport protocols including gRPC, REST, and WebSocket. The system is designed for reliable, graceful lifecycle management and offers client libraries in Go, Java, Python, and JavaScript for sending events.
59.7
Adequate · 3 August 2026
5.3k
lines of production code
Go
with JavaScript, Java
2
bus factor · 16 authors in all
3
measurements over time
How it got here
2020 · Release tooling and lifecycle management
This period focused on establishing robust release tooling and modernizing the application's lifecycle management. The project introduced structured configuration, automated cross-platform builds, and replaced manual shutdown logic with Go's context-based patterns. Additionally, legacy HTTP endpoints and outdated dependencies were removed or updated across all client libraries.
5 changes
2022–2023 · multi-language client libraries
This period focused on expanding the Raccoon ecosystem by releasing official client libraries for Go, Java, and JavaScript. Each release provided robust, configurable interfaces for sending events via REST, gRPC, and WebSocket transports, significantly broadening the service's accessibility across different programming environments.
4 changes
2024 · core infrastructure and client SDKs
This period focused on establishing the core event processing pipeline, introducing a CLI interface, and releasing Python client libraries. It also expanded the system's capabilities by adding new event publishers for various backends and implementing integration tests to validate error handling across multiple protocols.
5 changes
Survey your own repository
raystack/raccoon 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.
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 3 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 d6bf56fd21 — 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.