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

taloc0111/quanlycongno

https://github.com/taloc0111/quanlycongno · scanned 2026-06-16 00:29 UTC (2 months, 2 weeks ago)

97 raw signals (0 security + 97 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 96 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
55.0
/100
Security checks
55
0 findings
System graph
55
88.9% cov · 96 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 2 Medium 17 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 96 Crowd 0 Layer: Frontend 16 Security 7 Quality 22 Api 51

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

#1
Possible secret in backend/test-bcrypt.js
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 backend/test-bcrypt.js:4; move to env var / secrets manager.
backend/test-bcrypt.js:4
#2
Possible secret in backend/setup-admin.js
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 backend/setup-admin.js:11; move to env var / secrets manager.
backend/setup-admin.js:11
#3
Possible secret in backend/setup-admin.js
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 backend/setup-admin.js:12; move to env var / secrets manager.
backend/setup-admin.js:12
#4
Dangling fetch: POST https://api.resend.com/emails (backend/config/email.js:27)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#5
Dangling fetch: GET https://serpapi.com/search?${params} (backend/workers/lib/serpapi.js:73)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#6
Insecure pattern 'local_storage_auth_token' in website/src/DebtApp.jsx:263
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
website/src/DebtApp.jsx:263
#7
Insecure pattern 'local_storage_auth_token' in website/src/auth/AuthContext.jsx:24
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
website/src/auth/AuthContext.jsx:24
#8
Insecure pattern 'local_storage_auth_token' in website/src/backup/DebtApp.jsx:134
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
website/src/backup/DebtApp.jsx:134
#9
Insecure pattern 'local_storage_auth_token' in website/src/backup/App copy.jsx:134
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
website/src/backup/App copy.jsx:134
#10
Insecure pattern 'local_storage_auth_token' in website/src/backup/DebtApp copy.jsx:134
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
website/src/backup/DebtApp copy.jsx:134

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/20a5e8e1-ef7f-43f8-a7d5-319fcc81b21d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/20a5e8e1-ef7f-43f8-a7d5-319fcc81b21d/

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.