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.

RackulaLives/Rackula

https://github.com/RackulaLives/Rackula · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

332 raw signals (114 security + 218 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 218 actionable findings from 2 signal sources. 452 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 · 209 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 109 Medium 23 Low 48 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 209 Crowd 0 Layer: Quality 56 Security 10 Frontend 18 Network 1 Hardware 5 Cicd 3 Api 125

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

2 matching findings on this repo

low Old/deprecated-named symbol `invalidLegacy` in src/tests/session-storage.test.t…
info Commented-code block (6 lines) in src/lib/storage/adapt-legacy-layout.ts:207

View all legacy markers findings →

Commented-out code 32 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 eslint.config.js:123
info Commented-code block (5 lines) in api/src/security/storage-quota-middleware.ts:…
info Commented-code block (5 lines) in api/src/security/sessions.ts:3
info Commented-code block (5 lines) in api/src/routes/layouts.ts:114
info Commented-code block (6 lines) in api/src/routes/layouts.test.ts:85
info Commented-code block (7 lines) in api/src/storage/storage-contract.ts:130
info Commented-code block (5 lines) in api/src/storage/filesystem.ts:777
info Commented-code block (5 lines) in src/tests/collision.test.ts:232
info Commented-code block (5 lines) in src/tests/App.cleanupPrompt.test.ts:169
info Commented-code block (6 lines) in src/tests/dnd-between-racks.test.ts:282
info Commented-code block (5 lines) in src/tests/App.startScreen.test.ts:103
info Commented-code block (5 lines) in src/lib/stores/canvas.svelte.ts:430

View all commented-out code findings →

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

5 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/generate-gh-dash-config.js:184
medium Insecure pattern 'node_child_process' in vite.config.ts:4 vite.config.ts:4
medium Insecure pattern 'node_child_process' in vitest.config.ts:4 vitest.config.ts:4
medium Insecure pattern 'node_child_process' in scripts/generate-gh-dash-config.js:16 scripts/generate-gh-dash-config.js:16
info Commented-code block (8 lines) in eslint.config.js:123

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/437d0a01-8e70-47d4-bf1a-6e385349ef99/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/437d0a01-8e70-47d4-bf1a-6e385349ef99/

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.