DefiLlama/dimension-adapters

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.

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

Scan timing: clone 6.22s · analysis 23.6s · 8.9 MB · GitHub preflight 445ms

https://github.com/DefiLlama/dimension-adapters · scanned 2026-06-05 18:20 UTC (4 days, 19 hours ago) · 10 languages

1495 raw signals (85 security + 1410 graph) 11/13 scanners ran 3rd percentile · Typescript · large (100-500K LoC) System graph score 76 (lower by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 719 actionable findings from 2 signal sources. 71 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 693 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	20.0	0.15	3.00
`practices_score`	69.0	0.15	10.35
`code_quality`	80.0	0.10	8.00
Overall		1.00	55.4

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 2 Medium 412 Low 133 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 26 System graph 693 Crowd 0 Layer: Security 11 Quality 596 Cicd 2 Software 52 Api 1 Frontend 57

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.

Legacy markers 4 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

4 matching findings on this repo

low Old/deprecated-named symbol `legacy_fee_recipient_v2` in fees/clanker.ts:14
medium `fetch()` without try/.catch or AbortSignal — dexs/machinex-legacy.ts:5
low Old/deprecated-named symbol `bribes_contracts_v2` in dexs/shadow-legacy.ts:37
low Old/deprecated-named symbol `fetchLegacy` in dexs/alex/index.ts:55

View all legacy markers findings →

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

12 matching findings on this repo

info Commented-code block (5 lines) in users/chains.ts:170
info Commented-code block (6 lines) in users/compound-v2/index.ts:131
info Commented-code block (6 lines) in fees/hyperevm.ts:7
info Commented-code block (6 lines) in fees/frenflow.ts:64
info Commented-code block (7 lines) in fees/xmarket.ts:10
info Commented-code block (5 lines) in fees/bloom.ts:46
info Commented-code block (6 lines) in fees/minebean.ts:12
info Commented-code block (11 lines) in fees/ethena.ts:59
info Commented-code block (16 lines) in fees/aura.ts:47
info Commented-code block (6 lines) in fees/tickr.ts:8
info Commented-code block (10 lines) in fees/apex-omni.ts:70
info Commented-code block (6 lines) in fees/maestro.ts:29

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

info Commented-code block (7 lines) in fees/euler/config.ts:153
info Commented-code block (9 lines) in fees/lagoon/config.ts:127

View all config drift 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/cfe9cb19-83c3-4507-9e31-4359c64bcce0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cfe9cb19-83c3-4507-9e31-4359c64bcce0/

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.