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.

0xarkstar/PD-AIO-SDK

https://github.com/0xarkstar/PD-AIO-SDK · scanned 2026-06-16 03:38 UTC (2 months ago)

123 raw signals (0 security + 123 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 93 actionable findings from 1 signal source. 30 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 · 93 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 9 High 0 Medium 6 Low 63 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 93 Crowd 0 Layer: Api 1 Frontend 50 Network 2 Hardware 1 Security 9 Cicd 2 Quality 28

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 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 `lighterLegacy` in src/adapters/lighter/LighterAdap…

View all legacy markers findings →

Commented-out code 13 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 tests/integration/cross-adapter-contract.test…
info Commented-code block (5 lines) in tests/unit/paradex-websocket-wrapper.test.ts:…
info Commented-code block (5 lines) in tests/unit/gmx-adapter.test.ts:1414
info Commented-code block (6 lines) in scripts/check-pattern-a.ts:248
info Commented-code block (5 lines) in src/adapters/dydx/DydxAdapter.ts:142
info Commented-code block (6 lines) in src/adapters/gmx/GmxOrderBuilder.ts:268
info Commented-code block (8 lines) in src/adapters/lighter/signer/LighterSigner.ts:…
info Commented-code block (5 lines) in src/adapters/standx/StandxAdapter.ts:406
info Commented-code block (5 lines) in src/adapters/extended/ExtendedAdapter.ts:152
info Commented-code block (5 lines) in src/adapters/extended/types.ts:479
info Commented-code block (5 lines) in src/adapters/katana/KatanaAuth.ts:162
info Commented-code block (5 lines) in src/adapters/grvt/GRVTWebSocketWrapper.ts:87

View all commented-out code findings →

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

3 matching findings on this repo

low Stray `console.log` in TS/JS — src/utils/config.ts:107
critical Possible secret in tests/unit/config-adapter-alignment.test.ts tests/unit/config-adapter-alignment.test.ts:32
critical Possible secret in tests/unit/config.test.ts tests/unit/config.test.ts:291

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/b80517e6-794d-4827-850c-5805baa453b2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b80517e6-794d-4827-850c-5805baa453b2/

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.