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

Scan timing: clone 1.73s · analysis 2.41s · 2.1 MB · GitHub preflight 480ms

deepakmuvva99/backend_dasep

https://github.com/deepakmuvva99/backend_dasep.git · scanned 2026-05-22 12:44 UTC (2 weeks ago) · 10 languages

346 findings (112 legacy + 234 scanner) 11th percentile · Javascript · small (2-20K LoC) Scanner says 71 (lower by 28)

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

Complete repo analysis

Last scanned 2 weeks ago · v2 · 229 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
66.0
/100
Repobility
61
112 legacy
9-layer
71
100.0% cov · 117 gaps
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 62.7 0.25 15.68
testing_score 0.0 0.20 0.00
documentation_score 21.0 0.15 3.15
practices_score 52.0 0.15 7.80
code_quality 60.7 0.10 6.07
Overall 1.00 43.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 86 Medium 9 Low 119 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 112 9-layer 117 Crowd 0 Layer: Quality 70 Security 34 Cicd 6 Software 55 Frontend 13 Network 1 Hardware 5 Api 45

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

#1
Privileged port 465 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in Intern-batch-08/Digital-Eval-Backend/services/emailService.js is a real port, change the binding to ≥1024 or run behind a proxy.
Intern-batch-08/Digital-Eval-Backend/services/emailService.js
#2
Dockerfile runs as root: Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#3
Dockerfile runs as root: Intern-batch-08/Digital-Eval-Backend/Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#4
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#5
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#6
Stray `console.log` in TS/JS — generate_postman.js:202
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in generate_postman.js:202.
#7
Stray `console.log` in TS/JS — swagger.js:28
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in swagger.js:28.
#8
Stray `console.log` in TS/JS — app.js:36
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in app.js:36.
#9
Stray `console.log` in TS/JS — config/azureBlob.js:32
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in config/azureBlob.js:32.
#10
Stray `console.log` in TS/JS — config/database.js:22
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in config/database.js:22.

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/ba571f8b-93df-4f32-b06a-0a6dfddc3e7a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ba571f8b-93df-4f32-b06a-0a6dfddc3e7a/

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.