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.

dpkp/kafka-python

https://github.com/dpkp/kafka-python · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

154 raw signals (0 security + 154 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -12.5 (diff) · 125 actionable findings from 1 signal source. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 125 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 2 Medium 6 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 125 Crowd 0 Layer: Software 25 Network 3 Security 3 Cicd 2 Quality 92

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

3 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

info Commented-code block (7 lines) in kafka/record/legacy_records.py:15
low Old/deprecated-named symbol `test_proxy_url_takes_precedence_over_legacy` in te…

View all legacy markers findings →

Commented-out code 30 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 kafka/cluster.py:547
info Commented-code block (7 lines) in kafka/future.py:32
info Commented-code block (5 lines) in kafka/codec.py:190
info Commented-code block (8 lines) in kafka/consumer/subscription_state.py:261
info Commented-code block (6 lines) in kafka/consumer/fetcher.py:202
info Commented-code block (6 lines) in kafka/consumer/group.py:787
info Commented-code block (5 lines) in kafka/benchmarks/producer_performance.py:54
info Commented-code block (6 lines) in kafka/producer/transaction_manager.py:55
info Commented-code block (5 lines) in kafka/producer/record_accumulator.py:395
info Commented-code block (6 lines) in kafka/producer/kafka.py:956
info Commented-code block (6 lines) in kafka/producer/sender.py:274
info Commented-code block (7 lines) in kafka/record/legacy_records.py:15

View all commented-out code findings →

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

2 matching findings on this repo

low Stub function `configure` (body is just `pass`/`return`) — kafka/metrics/dict_r…
info Commented-code block (6 lines) in test/producer/test_kip679_config.py:9

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/3c30319b-3d2f-4ef6-80da-4e6d88ff1177/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3c30319b-3d2f-4ef6-80da-4e6d88ff1177/

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.