TypedDuck builds type-driven, static-analysis tooling for dynamic languages — starting with Rigor, a Ruby static analyzer.https://www.typedduck.fail/enhttps://www.typedduck.fail/blog/hello-typedduck/https://www.typedduck.fail/blog/hello-typedduck/Why this umbrella exists, and what to expect from the blog. Thu, 25 Jun 2026 00:00:00 GMT<p>This is the first post on the TypedDuck blog.</p> <p>TypedDuck started as one project — <a href="https://rigor.typedduck.fail/">Rigor</a>, a Ruby static analyzer — and grew a second, the <a href="https://rigor.typedduck.fail/chibirigor/">chibirigor</a> online book. They share a worldview more than a codebase: types are already there in dynamic languages at runtime, and the job is to surface them while you write, not after you ship.</p> <p>This site is the umbrella over those projects, and this blog is where the notes that don’t belong in any one project’s docs will live — design decisions, release notes, and the occasional detour into type theory. Posts are written in both English and Japanese.</p> <p>More soon.</p>meta