getlago/lago
GitHubOpen Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
- analytics
- billing
- clickhouse
- events
- fintech
- go
- ingestion
- invoices
- metering
- open-source
- payments
- pricing
- pricing-data-science
- react
- ruby
- self-hosted
- subscriptions
- usage-based-billing
- Stars:
- 10.8k
- Language:
- Go
- Default branch:
- main
- Last scored:
At a glance
- Rank
- #381 of 401
- #39 of 40 Go repos
- Checks passed
- 5 of 17
- Full list below
- Best set up for
- Devin
- Score 49.2
- Needs most work for
- Cursor
- Biggest fix: Cursor rules (.cursor/rules) (+11.5 pts)
What it has
What it's missing
What to fix first
Showing fixes for Claude Code
- 1AGENTS.md / CLAUDE.mdAdd an AGENTS.md covering project goals, layout, setup commands, and conventions. Aim for 800+ chars of real guidance (not boilerplate).+13.2 pts
- 2Dependency manifestCommit a proper manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) plus a lockfile.+9.2 pts
- 3Linter / formatter configConfigure a linter/formatter (ESLint+Prettier, Biome, Ruff, rustfmt+clippy, golangci-lint) and commit the config.+7.9 pts
Score for each AI agent
Each agent weighs the checks by its own docs. Under each score are its top three. How each agent is scored →
Does getlago/lago have agent instructions?
An AGENTS.md (or CLAUDE.md) at the root tells AI coding agents how to build, test and work in the repo. A few agents also read a file of their own.
- AGENTS.md / CLAUDE.md
- None at the root (no AGENTS.md, CLAUDE.md, AGENT.md, .claude/CLAUDE.md or .claude/AGENTS.md)
- Agent-specific files
- None: no GEMINI.md, .cursor/rules, .openhands/setup.sh, .aider.conf.yml or .agents/skills
- Repos that have one
- 23 of 40 Go repos · 221 of 401 repos on the leaderboard · See examples →
Get a starter AGENTS.md
From the files the checks found. Fill in the commands, then commit it at the root.
# AGENTS.md
Guidance for AI coding agents working in getlago/lago. Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics. Written mainly in Go.
## Where things are
- Test files are spread through the tree, e.g. `events-processor/cache/billable_metric_filters_test.go`.
- CI is defined in `.github/workflows`; read it for the exact install, lint and test steps.
- A reproducible environment is defined in `docker-compose.yml`.
- Follow the conventions in `CONTRIBUTING.md`.
## Commands
<!-- Fill in the exact commands CI runs. -->
- Install: TODO
- Test: TODO
- Lint: TODO
All 17 checks · 5 passed
How getlago/lago compares
- vs leaderboard average
- 22.4 pts below
- Average 66.8
- vs Go average
- 26.6 pts below
- Average 71.0
- Stars among Go repos
- #35 of 40
Missing here, and how many repos have it
- Dependency manifest · passed by 92% of leaderboard repos, 95% of Go repos
- Type configuration · passed by 68% of leaderboard repos, 93% of Go repos
- Linter / formatter config · passed by 65% of leaderboard repos, 70% of Go repos
Passes checks most repos miss
- Manageable size · only 16% of repos pass it
One fix for the most agents: Linter / formatter config would raise the score for all 9 agents, by up to 14.1 points.
Similar repos
Same language and host as this repo, closest in overall score.
- Go · 50.1k ★
- dagger/dagger59.3Go · 16.6k ★
- Go · 45.6k ★
- Go · 111.7k ★
- stretchr/testify55.6Go · 26.2k ★
- golang/go29.9Go · 139.6k ★
Same topics, any language
Repos tagged with the same GitHub topics, most shared first.
- Elixir · analytics, clickhouse, self-hosted
- C++ · analytics, clickhouse, self-hosted
- getnao/nao84.4TypeScript · analytics, self-hosted
- TypeScript · fintech
- Rust · self-hosted
- n8n-io/n8n83.6TypeScript · self-hosted
Add a badge to your README
Paste this at the top of the README. It shows the score, and links back to this page.
[](https://agentfriendlycode.com/repo/github/getlago/lago)Check the score on every pull request
A GitHub Action posts one comment per pull request with how the score changed and why.