donutloop/toolkit
This system is a Go utility toolkit providing a collection of concurrency primitives, error handling utilities, and infrastructure helpers. It offers reusable components for managing goroutine lifecycles, implementing retry and scheduling logic, and facilitating code generation through AST manipulation. The library also includes practical tools for debugging, event publishing, and HTTP client middleware composition.
65.9
Adequate · 3 August 2026
1.2k
lines of production code
Go
primary language
1
bus factor · 3 authors in all
3
measurements over time
How it got here
2017 · Concurrency and utility primitives
This period focused on expanding the toolkit with a comprehensive set of concurrency and utility primitives. Key additions include a FIFO scheduler, a promise executor, a concurrent runner with panic recovery, and a loop package for periodic execution. The release also introduced helper packages for retry logic, in-process event buses, debug utilities, lease management, and multi-error handling.
11 changes
2018–2020 · concurrency and code generation tools
This period focused on introducing concurrency support through a new worker pool and enhancing HTTP client capabilities with middleware support. Additionally, the project expanded its code generation and refactoring infrastructure by adding a command-line tool and internal AST manipulation utilities.
5 changes
Survey your own repository
donutloop/toolkit 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 7529a4e9d4 — 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.