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.

WayfinderFoundation/wayfinder-paths-sdk

https://github.com/WayfinderFoundation/wayfinder-paths-sdk · scanned 2026-06-16 00:55 UTC (2 months, 1 week ago)

171 raw signals (0 security + 171 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 129 actionable findings from 1 signal source. 42 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 · 129 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 13 Medium 38 Low 69 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 129 Crowd 0 Layer: Software 15 Api 1 Frontend 1 Security 14 Cicd 4 Quality 94

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `_publish_legacy` in wayfinder_paths/paths/client.p…

View all legacy markers findings →

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

6 matching findings on this repo

info Commented-code block (9 lines) in wayfinder_paths/adapters/hyperliquid_adapter/…
info Commented-code block (6 lines) in wayfinder_paths/mcp/tools/hyperliquid.py:1996
info Commented-code block (7 lines) in wayfinder_paths/core/constants/euler_v2_abi.p…
info Commented-code block (5 lines) in wayfinder_paths/core/clients/DeltaLabClient.p…
info Commented-code block (6 lines) in wayfinder_paths/strategies/boros_hype_strateg…
info Commented-code block (7 lines) in wayfinder_paths/strategies/basis_trading_stra…

View all commented-out code findings →

Config drift 11 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.

11 matching findings on this repo

high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:230
high Agent instruction/config may expose a secret: .claude/skills/writing-wayfinder-… .claude/skills/writing-wayfinder-scripts/SKILL.md:177
high Agent instruction/config may expose a secret: .claude/skills/using-hyperliquid-… .claude/skills/using-hyperliquid-adapter/rules/ex…:186
high Agent instruction/config may expose a secret: .claude/skills/using-aerodrome-sl… .claude/skills/using-aerodrome-slipstream-adapter…:81
high Agent instruction/config may expose a secret: .claude/skills/simulation-dry-run… .claude/skills/simulation-dry-run/rules/quickstar…:39
high Agent instruction/config may expose a secret: .claude/skills/using-polymarket-a… .claude/skills/using-polymarket-adapter/rules/dep…:24
high Agent instruction/config may expose a secret: .claude/skills/using-polymarket-a… .claude/skills/using-polymarket-adapter/rules/exe…:48
high Agent instruction/config may expose a secret: .claude/skills/using-pendle-adapt… .claude/skills/using-pendle-adapter/rules/executi…:45
high Agent instruction/config may expose a secret: .claude/skills/using-boros-adapte… .claude/skills/using-boros-adapter/rules/executio…:117
high Agent instruction/config may expose a secret: .claude/skills/using-aave-v3-adap… .claude/skills/using-aave-v3-adapter/rules/execut…:24
high Agent instruction/config may expose a secret: .claude/skills/setup/rules/api-ke… .claude/skills/setup/rules/api-key.md:25

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/b1f66ce4-fdb4-4970-98a0-0e1c94f639fa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b1f66ce4-fdb4-4970-98a0-0e1c94f639fa/

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.