sferik/twitter-ruby
This system is a Ruby gem that provides a comprehensive client library for interacting with the Twitter API. It offers a modular, object-oriented interface for managing REST resources such as tweets, users, and direct messages, alongside support for streaming endpoints and media handling. The library includes robust domain models for parsing API responses, type signatures for static analysis, and a modernized development environment.
54.5
Adequate · 2 August 2026
8.1k
lines of production code
Ruby
primary language
1
bus factor · 211 authors in all
3
measurements over time
How it got here
2006 · library restructuring and modernization
The project underwent a comprehensive restructuring of its library architecture, introducing a modular, object-oriented interface with extensive new domain models and client infrastructure for the Twitter API. This period also involved modernizing the project's tooling, configuration, and development workflows while removing legacy code and generated documentation.
6 changes
2007–2012 · Test coverage and entity expansion
This period focused on modernizing the testing infrastructure by migrating to Minitest and integrating coverage tools, while simultaneously expanding the library's feature set to support new Twitter API entities like animated GIFs, videos, and various metadata types. The work also involved adding comprehensive test fixtures and unit tests to ensure the correct behavior of these new and existing components.
6 changes
2013–2026 · Architecture modernization and type safety
The codebase underwent a significant architectural refactoring, splitting the REST client into modular components and introducing a new streaming client. Development also focused on expanding feature support for direct messages and establishing static type checking via RBS signatures to improve code maintainability and developer experience.
6 changes
Survey your own repository
sferik/twitter-ruby 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 2 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 c535a3c97d — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.