basho/riak_cs
This system is a distributed object storage service (Riak CS) that implements the S3 API, supporting core operations such as bucket and object management, access control, and garbage collection. It provides a comprehensive testing framework that validates compatibility across multiple client libraries in Python, Ruby, PHP, and Clojure, alongside internal diagnostic tools for maintenance and debugging. The architecture emphasizes reliability through extensive automated testing, including property-based and compatibility tests, ensuring robust handling of storage, replication, and state management.
45.3
Weak · 1 August 2026
65k
lines of production code
Erlang
primary language
3
bus factor · 56 authors in all
3
measurements over time
How it got here
2011–2012 · Release infrastructure and test harness development
This period focused on establishing the foundational build system, release packaging, and administrative utilities for Riak CS 2.1.0. Significant effort was also directed toward expanding automated testing coverage through new Erlang and Clojure test suites, alongside the implementation of access logging and object listing features.
13 changes
2013 · client test coverage expansion
This period focused on expanding automated testing across multiple client languages, including PHP, Python, and Ruby, to validate S3 API compatibility. Internal diagnostic and cleanup tools were also added to support debugging and maintenance of the storage system.
9 changes
2014–2015 · Development and testing infrastructure
This period focused on enhancing the development and testing environment for Riak CS. Key additions included a local development configuration, an S3 client library for AWS integration, and intercept modules to simulate error conditions during testing. Additionally, a repair script was introduced to handle invalid state manifests in the garbage collection bucket.
4 changes
Survey your own repository
basho/riak_cs 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 1 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 c0c1012d1c — 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.