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.

solana-foundation/solana-developer-platform

https://github.com/solana-foundation/solana-developer-platform · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

862 raw signals (155 security + 707 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 686 actionable findings from 2 signal sources. 380 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 · 677 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 499 Medium 48 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 677 Crowd 0 Layer: Quality 72 Security 15 Frontend 46 Network 3 Hardware 1 Cicd 3 Api 546

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

3 matching findings on this repo

low Old/deprecated-named symbol `cust_cfg_dfns_legacy` in apps/sdp-api/src/routes/c…
low Old/deprecated-named symbol `wal_legacy` in apps/sdp-api/src/services/api-key-s…
low Old/deprecated-named symbol `org_dfns_legacy` in apps/sdp-api/src/services/doma…

View all legacy markers findings →

Commented-out code 16 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 (8 lines) in apps/sdp-docs/next.config.mjs:30
info Commented-code block (7 lines) in apps/sdp-api/src/server.ts:140
info Commented-code block (5 lines) in apps/sdp-api/src/types/env.d.ts:32
info Commented-code block (5 lines) in apps/sdp-api/src/routes/issuance.test.ts:2782
info Commented-code block (5 lines) in apps/sdp-api/src/routes/issuance/handlers/min…
info Commented-code block (5 lines) in apps/sdp-api/src/routes/payments/schemas.ts:13
info Commented-code block (8 lines) in apps/sdp-api/src/runtime/observability-node.t…
info Commented-code block (6 lines) in apps/sdp-api/src/runtime/shutdown-node.ts:30
info Commented-code block (5 lines) in apps/sdp-api/src/runtime/background-node.ts:26
info Commented-code block (7 lines) in apps/sdp-api/src/runtime/observability-cf.tes…
info Commented-code block (5 lines) in apps/sdp-api/src/cron/pending-transfers.ts:28
info Commented-code block (5 lines) in apps/sdp-api/src/services/token.service.ts:13…

View all commented-out code findings →

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

12 matching findings on this repo

medium `dangerouslySetInnerHTML` used in a React component — apps/sdp-docs/src/compone…
medium Insecure pattern 'dangerous_innerhtml' in apps/sdp-docs/src/components/EnvConfi… apps/sdp-docs/src/components/EnvConfigurator/inde…:599
critical Insecure pattern 'private_key_in_repo' in packages/sdp-env-config/src/validate.… packages/sdp-env-config/src/validate.test.ts:94
low Node manifest has dependencies but no lockfile: packages/sdp-env-config/package… packages/sdp-env-config/package.json
info Commented-code block (8 lines) in apps/sdp-docs/next.config.mjs:30
info Commented-code block (7 lines) in apps/sdp-web/next.config.ts:36
high Dangling fetch: GET /v1/wallets/configs (apps/sdp-api/src/routes/custody-wallet…
high Dangling fetch: GET /v1/wallets/configs (apps/sdp-api/src/routes/custody-multi-…
high Dangling fetch: GET /v1/wallets/configs (apps/sdp-api/src/routes/custody-multi-…
high Dangling fetch: GET /v1/wallets/config (apps/sdp-api/src/routes/custody-multi-p…
high Dangling fetch: GET /v1/wallets/configs (apps/sdp-web/src/app/api/dashboard/wal…
high Dangling fetch: GET /v1/wallets/configs (apps/sdp-web/src/app/dashboard/custody…

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/dd6f9a54-4bed-4241-8c43-2aea58e57c15/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dd6f9a54-4bed-4241-8c43-2aea58e57c15/

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.