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 (14 hours, 26 minutes ago) · 10 languages

2613 findings (201 legacy + 2412 scanner) 8/10 scanners ran Scanner says 59 (higher by 20)

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

Complete repo analysis

Last scanned 14 hours, 26 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
69.5
/100
Repobility
80
201 legacy
9-layer
59
100.0% cov · 2412 gaps
Critical
29
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: severity: critical × excluding tests × Reset all
Severity: Critical 29 High 70 Medium 126 Low 2364 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
Scan summary Repository scanned at 59.3/100 with 100.0% coverage. It contains 17886 nodes across 19 cross-layer flows, written primarily in mixed languages. Engine surfaced 2412 findings — concentrated in frontend (2040), quality (159), cicd (111). Risk profile is high: 21 critical, 26 high, 43 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 22 of 2613 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
crates/hsdev/src/input_file.rs:22 credential_exposurelegacy
critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
crates/common_utils/src/lib.rs:324 credential_exposurelegacy
critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
crates/analytics/src/sqlx.rs:45 credential_exposurelegacy
critical Legacy cicd docker conf 0.96 Compose service contains a literal secret environment value
Rotate the value if real. Move it to Docker Compose secrets, a platform secret manager, or an uncommitted environment file.
docker-compose.yml:522 dockerlegacy
critical Legacy cicd docker conf 0.96 Compose service contains a literal secret environment value
Rotate the value if real. Move it to Docker Compose secrets, a platform secret manager, or an uncommitted environment file.
docker-compose.yml:480 dockerlegacy
critical Legacy cicd docker conf 0.96 Compose service contains a literal secret environment value
Rotate the value if real. Move it to Docker Compose secrets, a platform secret manager, or an uncommitted environment file.
docker-compose.yml:26 dockerlegacy
critical Legacy cicd docker conf 0.98 Compose service mounts the Docker socket
Avoid mounting docker.sock. Use a narrow proxy, rootless build service, or provider-native deployment credentials.
docker-compose.yml:506 dockerlegacy
critical 9-layer security owasp conf 1.00 Insecure pattern 'private_key_in_repo' in crates/connector_configs/toml/development.toml:5893
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
crates/connector_configs/toml/development.toml:5893 owaspprivate_key_in_repo
critical 9-layer security owasp conf 1.00 Insecure pattern 'private_key_in_repo' in crates/connector_configs/toml/production.toml:5658
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
crates/connector_configs/toml/production.toml:5658 owaspprivate_key_in_repo
critical 9-layer security owasp conf 1.00 Insecure pattern 'private_key_in_repo' in crates/connector_configs/toml/sandbox.toml:5857
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
crates/connector_configs/toml/sandbox.toml:5857 owaspprivate_key_in_repo
critical 9-layer security secrets conf 1.00 Possible secret in config/deployments/drainer.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/deployments/drainer.toml:34 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/development.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/development.toml:24 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/development.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/development.toml:34 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/development.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/development.toml:1365 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/development.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/development.toml:1392 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/docker_compose.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/docker_compose.toml:31 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/docker_compose.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/docker_compose.toml:46 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/docker_compose.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/docker_compose.toml:1190 secrets
critical 9-layer security secrets conf 1.00 Possible secret in config/docker_compose.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
config/docker_compose.toml:1227 secrets
critical 9-layer security secrets conf 1.00 Possible secret in crates/hsdev/src/main.rs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
crates/hsdev/src/main.rs:103 secrets
critical 9-layer security secrets conf 1.00 Possible secret in crates/hsdev/src/main.rs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
crates/hsdev/src/main.rs:124 secrets
critical 9-layer security secrets conf 1.00 Possible secret in scripts/create_default_user.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/create_default_user.sh:3 secrets
{# ── 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.