beam-community/stripity-stripe
This system is an Elixir client library for the Stripe API, designed to facilitate secure and structured interaction with Stripe's payment and financial services. It provides a comprehensive suite of modules for managing core resources like customers, charges, and subscriptions, alongside specialized integrations for Stripe Connect, Identity, and Webhooks. The library leverages OpenAPI specifications to generate and maintain up-to-date client code, ensuring accurate representation of current API objects and error structures.
58.0
Adequate · 1 August 2026
46k
lines of production code
Elixir
primary language
6
bus factor · 192 authors in all
3
measurements over time
How it got here
2015 · Library rebuild and modernization
The project underwent a complete architectural overhaul, replacing the previous high-level API with a functional request builder and object converter. This period focused on modernizing dependencies, implementing OpenAPI code generation, and establishing a robust test suite using Stripe Mock and Mox.
6 changes
2016–2017 · Stripe Connect and test coverage expansion
This period focused on integrating Stripe Connect OAuth functionality and significantly expanding test coverage across core, subscription, and payment method resources. The team also established a robust testing infrastructure using mock servers and helper modules to verify API interactions.
7 changes
2019–2023 · OpenAPI code generation and test coverage
This period focused on automating the generation of the client library from the Stripe OpenAPI specification, introducing a new internal code-generation pipeline. Concurrently, significant test coverage was added for multiple Stripe API resources, including Checkout, Billing Portal, Identity, and Fraud services.
6 changes
Survey your own repository
beam-community/stripity-stripe 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 a364904bd6 — 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.