getlago/lago-api

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

29 of your 113 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.51s · analysis 16.06s · 21.7 MB · GitHub API rate-limit (preflight)

https://github.com/getlago/lago-api · scanned 2026-06-05 12:59 UTC (5 days, 9 hours ago) · 10 languages

233 raw signals (105 security + 128 graph) 11/13 scanners ran

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 84 actionable findings from 2 signal sources. 85 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 24 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	91.0	0.15	13.65
`code_quality`	80.0	0.10	8.00
Overall		1.00	67.7

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 16 High 37 Medium 10 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 60 System graph 24 Crowd 0 Layer: Quality 11 Security 49 Cicd 13 Software 5 Api 1 Hardware 4 Frontend 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

low File has no detected symbols: app/assets/config/manifest.js
critical Possible secret in spec/lib/lago/redis_config_builder_spec.rb spec/lib/lago/redis_config_builder_spec.rb:59
critical Possible secret in config/i18n-tasks.yml config/i18n-tasks.yml:110
medium Insecure pattern 'weak_hash' in config/application.rb:34 config/application.rb:34

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/d5bbf7bb-a3db-4b3d-8722-27b2b726c0b2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d5bbf7bb-a3db-4b3d-8722-27b2b726c0b2/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.