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 (18 hours, 21 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 18 hours, 22 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

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.

Fragile runtime 70 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/refunds_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/payouts_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/payments_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/merchant_connector_we…:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/fraud_check_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/files_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/disputes_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/types/api/authentication_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/core/webhooks/outgoing_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/core/webhooks/incoming_v2.rs:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/core/payments/operations/paymen…:1
  • medium Parallel implementation file sits beside a canonical file crates/router/src/core/payments/operations/paymen…:1
View all fragile runtime findings →
Commented-out code 13 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (8 lines) in cypress-tests/cypress/e2e/configs/Payment/Aut…
  • info Commented-code block (20 lines) in cypress-tests/cypress/e2e/configs/Payment/Fi…
  • info Commented-code block (10 lines) in cypress-tests/cypress/e2e/configs/Payment/Si…
  • info Commented-code block (12 lines) in cypress-tests/cypress/e2e/configs/Payment/St…
  • info Commented-code block (12 lines) in cypress-tests/cypress/e2e/configs/Payment/St…
  • info Commented-code block (9 lines) in cypress-tests/cypress/e2e/configs/Payment/Cel…
  • info Commented-code block (5 lines) in cypress-tests/cypress/e2e/configs/mock-server…
  • info Commented-code block (8 lines) in postman/collection-dir/bankofamerica/Flow Tes…
  • info Commented-code block (5 lines) in postman/collection-dir/braintree/Flow Testcas…
  • info Commented-code block (6 lines) in postman/collection-dir/braintree/Flow Testcas…
  • info Commented-code block (7 lines) in postman/collection-dir/adyen_uk/Flow Testcase…
  • info Commented-code block (5 lines) in postman/collection-dir/checkout/Flow Testcase…
View all commented-out code findings →
Config drift 43 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.
12 matching findings on this repo
  • low File has no detected symbols: cypress-tests/eslint.config.js
  • low File has no detected symbols: cypress-tests/cypress.config.js
  • low File has no detected symbols: cypress-tests/cypress/e2e/spec/Misc/00001-MemoryC…
  • low File has no detected symbols: cypress-tests/cypress/e2e/spec/Payment/28-Busines…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress.config.js:30
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/Payment/WorldP…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/Payment/Common…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/mock-server/mo…
  • info TODO/FIXME marker in shipping code — cypress-tests/cypress/e2e/configs/mock-ser…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/mock-server/ro…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/mock-server/Co…
  • low Stray `console.log` in TS/JS — cypress-tests/cypress/e2e/configs/mock-server/Co…
View all config drift findings →
{# ── 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.