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.

Scan timing: clone 16.72s · analysis 2.4s · 0.8 MB · GitHub preflight 3582ms

totosugito/fin-man

https://github.com/totosugito/fin-man · scanned 2026-05-29 10:06 UTC (1 week ago) · 10 languages

196 findings (50 legacy + 146 scanner) 6th percentile · Typescript · medium (20-100K LoC) Scanner says 81 (lower by 34)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week ago · v2 · 123 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 70.3 0.25 17.57
testing_score 12.0 0.20 2.40
documentation_score 9.0 0.15 1.35
practices_score 40.0 0.15 6.00
code_quality 67.1 0.10 6.71
Overall 1.00 46.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Possible secret in src/locale/id.ts
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 src/locale/id.ts:22; move to env var / secrets manager.
src/locale/id.ts:22
#2
Possible secret in src/locale/id.ts
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 src/locale/id.ts:44; move to env var / secrets manager.
src/locale/id.ts:44
#3
Possible secret in src/locale/id.ts
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 src/locale/id.ts:82; move to env var / secrets manager.
src/locale/id.ts:82
#4
.env file present in repo: .env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#5
.env file present in repo: backend/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#6
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#7
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#8
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#9
`fetch()` without try/.catch or AbortSignal — src/lib/auth-client.ts:7
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/lib/auth-client.ts:7, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
Stray `console.log` in TS/JS — backend/src/scripts/init-data.ts:70
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in backend/src/scripts/init-data.ts:70.

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/ee7d3aaf-6c31-433d-b721-478c750ea54b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ee7d3aaf-6c31-433d-b721-478c750ea54b/

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.