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.

Rtoony/rtoony-portal

https://github.com/Rtoony/rtoony-portal · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

474 raw signals (0 security + 474 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 439 actionable findings from 1 signal source. 35 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 · 439 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 256 Medium 14 Low 105 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 439 Crowd 0 Layer: Software 20 Frontend 53 Security 218 Cicd 1 Quality 93 Api 54

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

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 20 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.

12 matching findings on this repo

low Very large file: server/routes/ingestion/legacy.py (3233 lines)
low Old/deprecated-named symbol `intake_legacy` in server/tests/test_operator_pack.…
low Old/deprecated-named symbol `migrated_legacy` in server/routes/ingestion/topics…
low Old/deprecated-named symbol `migrated_legacy` in server/routes/ingestion/shared…
high FastAPI PATCH `update_source_policy` without auth dependency — server/routes/in… server/routes/ingestion/legacy.py:397
high FastAPI POST `analyze_source_intake` without auth dependency — server/routes/in… server/routes/ingestion/legacy.py:916
high FastAPI POST `import_once_source` without auth dependency — server/routes/inges… server/routes/ingestion/legacy.py:1019
high FastAPI POST `create_source_intake_draft` without auth dependency — server/rout… server/routes/ingestion/legacy.py:1231
high FastAPI POST `promote_source_intake_draft` without auth dependency — server/rou… server/routes/ingestion/legacy.py:1299
high FastAPI POST `run_inspect_action` without auth dependency — server/routes/inges… server/routes/ingestion/legacy.py:1391
high FastAPI POST `run_stage_source_action` without auth dependency — server/routes/… server/routes/ingestion/legacy.py:1414
high FastAPI POST `run_promote_evidence_action` without auth dependency — server/rou… server/routes/ingestion/legacy.py:1445

View all legacy markers findings →

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

11 matching findings on this repo

info Commented-code block (5 lines) in client/src/components/ui/flow-map.tsx:116
info Commented-code block (7 lines) in client/src/components/hermes/types.ts:1
info Commented-code block (5 lines) in client/src/lib/portal-nav.ts:63
info Commented-code block (5 lines) in server/xkeys_service.py:1638
info Commented-code block (5 lines) in server/config.py:17
info Commented-code block (5 lines) in server/app.py:260
info Commented-code block (7 lines) in server/lib/services_registry.py:3
info Commented-code block (5 lines) in server/lib/autoresearch_nightly.py:460
info Commented-code block (5 lines) in server/routes/splat.py:649
info Commented-code block (5 lines) in server/routes/claws_sessions.py:387
info Commented-code block (7 lines) in server/routes/ingestion/topics.py:440

View all commented-out code findings →

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

4 matching findings on this repo

info Commented-code block (5 lines) in server/config.py:17
high FastAPI PUT `update_gesture_config` without auth dependency — server/routes/vis… server/routes/vision.py:329
high FastAPI POST `update_config` without auth dependency — server/routes/xkeys.py:33 server/routes/xkeys.py:33
low Unused endpoint: GET /map-config

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/c4c5143c-0431-46d5-b2e5-2719aec4a1e1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c4c5143c-0431-46d5-b2e5-2719aec4a1e1/

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.