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

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 60.8/100 with 100.0% coverage. It contains 2073 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 123 findings — concentrated in frontend (50), security (30), quality (28). Risk profile is high: 30 critical, 0 high, 6 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 69 of 93 actionable findings. 123 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/adapters/nado/NadoAdapter.ts:257

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/resilience.ts:214

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 15 placeholder/mock markers across 6 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph network Security conf 1.00 Privileged port 15 in use

Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

monitoring/alertmanager/config.yml Ports

medium System graph network Security conf 1.00 Privileged port 4 in use

Port 4 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

monitoring/alertmanager/config.yml Ports

low System graph quality Integrity conf 1.00 6 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `EXTENDED_STARKNET_ACCOUNT_ADDRESS`, `EXTENDED_STARKNET_PRIVATE_KEY`, `LIGHTER_API_PRIVATE_KEY`, `PRIVATE_KEY`, `STARKNET_ACCOUNT_ADDRESS`, `STARKNET_PRIVATE_KEY`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 744 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 10 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

3 files, 10 locations

.github/workflows/api-compatibility.yml:29, 32, 55, 63, 82 (5 hits)

.github/workflows/production-tests.yml:38, 41, 133, 180 (4 hits)

.github/workflows/pr-validation.yml:18

CI/CD securitySupply chainGithub actions

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

package.json LockfileReproducibilityGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lighterLegacy` in src/adapters/lighter/LighterAdapter.ts:96

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — examples/01-basic-trading.ts:22