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

hyperswitch

https://github.com/juspay/hyperswitch.git · scanned 2026-05-17 02:58 UTC (17 hours, 28 minutes ago) · 10 languages

2613 findings (201 legacy + 2412 scanner) 8/10 scanners ran

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 17 hours, 28 minutes ago · v2 · 2613 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
55.0
/100
Repobility
51
201 legacy
9-layer
59
100.0% cov · 2412 gaps
Critical
29
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 32.6 0.25 8.15
testing_score 80.0 0.20 16.00
documentation_score 70.0 0.15 10.50
practices_score 75.0 0.15 11.25
code_quality 43.6 0.10 4.36
Overall 1.00 59.3
Calibrated penalty buckets (security_score): agent: 6.4 · docker: 148.4 · threat: 36.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 29 High 50 Medium 126 Low 2384 Source: Legacy 201 9-layer 2412 Crowd 0 Layer: Quality 228 Cicd 229 Software 59 Security 30 Frontend 2040 Network 1 Hardware 8 Api 18

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

#1
Possible secret in config/development.toml
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/development.toml:24; move to env var / secrets manager.
config/development.toml:24
#2
Possible secret in config/development.toml
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/development.toml:34; move to env var / secrets manager.
config/development.toml:34
#3
Possible secret in config/development.toml
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/development.toml:1365; move to env var / secrets manager.
config/development.toml:1365
#4
Possible secret in config/development.toml
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/development.toml:1392; move to env var / secrets manager.
config/development.toml:1392
#5
Possible secret in config/docker_compose.toml
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/docker_compose.toml:31; move to env var / secrets manager.
config/docker_compose.toml:31
#6
Possible secret in config/docker_compose.toml
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/docker_compose.toml:46; move to env var / secrets manager.
config/docker_compose.toml:46
#7
Possible secret in config/docker_compose.toml
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/docker_compose.toml:1190; move to env var / secrets manager.
config/docker_compose.toml:1190
#8
Possible secret in config/docker_compose.toml
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/docker_compose.toml:1227; move to env var / secrets manager.
config/docker_compose.toml:1227
#9
Possible secret in config/deployments/drainer.toml
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/deployments/drainer.toml:34; move to env var / secrets manager.
config/deployments/drainer.toml:34
#10
Possible secret in config/deployments/env_specific.toml
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/deployments/env_specific.toml:10; move to env var / secrets manager.
config/deployments/env_specific.toml:10

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.

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/9c39f054-10cb-4584-aa89-251222603de5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9c39f054-10cb-4584-aa89-251222603de5/

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.