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.

redis/RedisInsight

https://github.com/redis/RedisInsight · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

482 raw signals (0 security + 482 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 27 High 13 Medium 58 Low 107 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 400 Crowd 0 Layer: Frontend 181 Network 13 Hardware 40 Security 50 Cicd 6 Quality 60 Api 50

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

6 matching findings on this repo

low Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/redis:6.0.8
low Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/redis-clus… redisinsight/api/test/test-runs/oss-clu/Dockerfile:1
low Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/redis-clus… redisinsight/api/test/test-runs/oss-clu-tls/Docke…:1
low Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/redis:6.2.4 redisinsight/api/test/test-runs/oss-st-6-tls/Dock…:1
low Old/deprecated-named symbol `BrowserLeftPanelLegacy` in redisinsight/ui/src/pag…
low Old/deprecated-named symbol `BrowserLeftPanelLegacy` in redisinsight/ui/src/pag…

View all legacy markers findings →

Commented-out code 39 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 .eslintrc.js:197
info Commented-code block (7 lines) in tests/e2e-playwright/playwright.config.ts:58
info Commented-code block (18 lines) in redisinsight/api/test/api/enterprise/POST-re…
info Commented-code block (6 lines) in redisinsight/api/test/api/cloud/autodiscovery…
info Commented-code block (8 lines) in redisinsight/api/test/api/database/POST-datab…
info Commented-code block (5 lines) in redisinsight/api/test/api/redisearch/POST-dat…
info Commented-code block (8 lines) in redisinsight/api/test/api/bulk-actions/POST-d…
info Commented-code block (6 lines) in redisinsight/api/src/__mocks__/redis-database…
info Commented-code block (5 lines) in redisinsight/api/src/modules/redis-sentinel/r…
info Commented-code block (12 lines) in redisinsight/api/src/modules/cloud/job/jobs/…
info Commented-code block (10 lines) in redisinsight/api/src/modules/profiler/monito…
info Commented-code block (6 lines) in redisinsight/api/src/modules/redis/client/red…

View all commented-out code findings →

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

8 matching findings on this repo

info TODO/FIXME marker in shipping code — redisinsight/api/src/modules/feature/local…
info TODO/FIXME marker in shipping code — redisinsight/ui/src/config/default.ts:57
medium Insecure pattern 'node_child_process' in redisinsight/api/config/default.ts:3 redisinsight/api/config/default.ts:3
info Commented-code block (7 lines) in tests/e2e-playwright/playwright.config.ts:58
info Commented-code block (5 lines) in redisinsight/ui/vite.config.mjs:96
info Commented-code block (7 lines) in configs/webpack.config.main.prod.ts:40
low Unused endpoint: GET /slow-logs/config
low Unused endpoint: PATCH /slow-logs/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/5cb3c917-74a9-4ce1-9ace-c047ab999a25/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5cb3c917-74a9-4ce1-9ace-c047ab999a25/

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.