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.

40 of your 82 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.8s · analysis 18.69s · 6.1 MB · GitHub API rate-limit (preflight)

0gam24/moneylook

https://github.com/0gam24/moneylook · scanned 2026-06-16 03:37 UTC (2 months ago) · 10 languages

116 raw signals (77 security + 39 graph) 50th percentile · Typescript · small (2-20K LoC) System graph score 54 (higher by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 29 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	58.1	0.25	14.53
`testing_score`	100.0	0.20	20.00
`documentation_score`	48.0	0.15	7.20
`practices_score`	79.0	0.15	11.85
`code_quality`	74.8	0.10	7.48
Overall		1.00	76.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 12 Medium 22 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 36 System graph 29 Crowd 0 Layer: Software 20 Security 10 Cicd 5 Quality 25 Network 5

Exclude dismissed / FP Exclude test files

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.

Commented-out code 3 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/`.

3 matching findings on this repo

info Commented-code block (14 lines) in scripts/audit/revenue-pull.mjs:6
info Commented-code block (6 lines) in scripts/audit/gsc-opportunities.mjs:10
info Commented-code block (5 lines) in src/lib/ads-lazy.ts:1

View all commented-out code findings →

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/6c9075fa-1280-4eb0-8a20-5046b98eee3f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6c9075fa-1280-4eb0-8a20-5046b98eee3f/

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.