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.
Sign up free Scan another repo
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)

getlago/lago-api

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
Combined
72.8
/100
Security checks
78
60 findings
System graph
68
100.0% cov · 24 findings
Critical
16
click to filter
Agents
6
0 votes
Crowd
0
reported
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in config/i18n-tasks.yml
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in config/i18n-tasks.yml:110; move to env var / secrets manager.
config/i18n-tasks.yml:110
#2
Possible secret in app/models/concerns/organizations/authentication_methods.rb
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/models/concerns/organizations/authentication_methods.rb:7; move to env var / secrets manager.
app/models/concerns/organizations/authentication_methods.rb:7
#3
Possible secret in db/seeds/01_base.rb
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in db/seeds/01_base.rb:37; move to env var / secrets manager.
db/seeds/01_base.rb:37
#4
Possible secret in db/seeds/01_base.rb
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in db/seeds/01_base.rb:45; move to env var / secrets manager.
db/seeds/01_base.rb:45
#5
Possible secret in db/seeds/01_base.rb
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in db/seeds/01_base.rb:27; move to env var / secrets manager.
db/seeds/01_base.rb:27
#6
Possible secret in db/seeds/01_base.rb
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in db/seeds/01_base.rb:30; move to env var / secrets manager.
db/seeds/01_base.rb:30
#7
Possible secret in .github/workflows/spec.yml
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in .github/workflows/spec.yml:53; move to env var / secrets manager.
.github/workflows/spec.yml:53
#8
Possible secret in .github/workflows/migrations-test.yml
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in .github/workflows/migrations-test.yml:38; move to env var / secrets manager.
.github/workflows/migrations-test.yml:38
#9
Insecure pattern 'weak_hash' in config/application.rb:34
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
config/application.rb:34
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/spec.yml:71

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.