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.

apache/doris

https://github.com/apache/doris · scanned 2026-06-26 22:37 UTC (1 month ago)

911 raw signals (0 security + 911 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month ago · v3 · 838 actionable findings from 1 signal source. 73 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 · 838 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 23 High 43 Medium 180 Low 215 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 838 Crowd 0 Layer: Software 20 Frontend 8 Security 164 Quality 568 Network 62 Hardware 12 Cicd 4

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

5 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 5 places
low Near-duplicate function bodies in 9 places
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

Commented-out code 376 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 (7 lines) in webroot/be/doris.js:1
info Commented-code block (7 lines) in .github/scripts/emit_litefuse_otel_io.py:2
info Commented-code block (5 lines) in build-support/run_clang_format.py:165
info Commented-code block (7 lines) in tools/profile_viewer.py:2
info Commented-code block (7 lines) in tools/qerror.py:2
info Commented-code block (7 lines) in tools/auto-pick-script.py:2
info Commented-code block (7 lines) in tools/show_segment_status/be_tablet_reslover.…
info Commented-code block (7 lines) in tools/show_segment_status/fe_meta_resolver.py…
info Commented-code block (7 lines) in tools/show_segment_status/show_segment_status…
info Commented-code block (7 lines) in tools/cost_model_evaluate/index_calculator.py…
info Commented-code block (7 lines) in tools/cost_model_evaluate/sql_executor.py:1
info Commented-code block (7 lines) in tools/cost_model_evaluate/evaluator.py:1

View all commented-out code findings →

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

10 matching findings on this repo

medium eval detected — pytest/lib/palo_config.py:223
low Very large file: fe/fe-common/src/main/java/org/apache/doris/common/Config.java…
info Commented-code block (7 lines) in tools/cost_model_evaluate/config.py:1
info Commented-code block (8 lines) in pytest/deploy/config_be.py:2
info Commented-code block (8 lines) in pytest/deploy/env_config.py:2
info Commented-code block (8 lines) in pytest/deploy/process_config_file.py:2
info Commented-code block (8 lines) in pytest/lib/palo_config.py:2
info Commented-code block (8 lines) in pytest/lib/kafka_config.py:2
info Commented-code block (7 lines) in ui/postcss.config.js:1
info Commented-code block (7 lines) in ui/webpack.config.js:1

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/6bc6e530-f738-4031-b245-811bd407411e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6bc6e530-f738-4031-b245-811bd407411e/

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.