leo-project/leofs
LeoFS is a distributed object storage system designed to provide S3-compatible and HTTP-based storage services. It comprises three primary components: a gateway for handling client requests, a manager for cluster coordination and configuration, and storage nodes for data persistence. The system supports multi-datacenter replication, rack awareness, and comprehensive monitoring via SNMP and Prometheus metrics. Additionally, it offers NFS access and integrates with various client SDKs for testing and benchmarking.
41.5
Weak · 1 August 2026
34k
lines of production code
Erlang
primary language
1
bus factor · 21 authors in all
3
measurements over time
How it got here
2012–2013 · Release packaging and deployment infrastructure
This period focused on establishing the build, release, and deployment infrastructure for LeoFS components. The work involved creating reltool configurations, startup scripts, and SmartOS packaging for the gateway, manager, and storage nodes. Additionally, test coverage was expanded with new benchmarking and S3 authentication test utilities.
14 changes
2015–2017 · Gateway release and infrastructure modernization
This period focused on the initial release and stabilization of the LeoFS Gateway, alongside a comprehensive modernization of the entire stack's configuration and deployment infrastructure. The team introduced Cuttlefish-based INI-style configuration, added systemd support, and integrated SNMP/Prometheus monitoring across all components to improve operational visibility and ease of use.
28 changes
2018 · Docker-based build and test automation
This period focused on establishing automated build and testing infrastructure using Docker. The team created environments for packaging LeoFS releases across multiple Linux distributions and containerized integration tests for various client libraries and protocols.
8 changes
Survey your own repository
leo-project/leofs 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 4ff701e0f4 — 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.