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.

zhebinliu/knowledge-base

https://github.com/zhebinliu/knowledge-base · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

317 raw signals (5 security + 312 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 257 actionable findings from 2 signal sources. 64 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 · 252 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 26 Medium 61 Low 116 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 252 Crowd 0 Layer: Quality 75 Security 57 Software 17 Frontend 47 Hardware 6 Cicd 3 Api 52

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

View all duplicates & near-duplicates findings →

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

4 matching findings on this repo

low Old/deprecated-named symbol `isLegacy` in frontend/src/components/TemplateSelec…
low Old/deprecated-named symbol `isLegacy` in frontend/src/redesign/console/Templat…
low Old/deprecated-named symbol `isLegacy` in meeting/frontend/src/components/Templ…
low Old/deprecated-named symbol `isLegacy` in meeting/frontend/src/redesign/console…

View all legacy markers findings →

Commented-out code 15 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 (6 lines) in frontend/src/main.tsx:11
info Commented-code block (5 lines) in frontend/src/components/console/research/Rese…
info Commented-code block (6 lines) in frontend/src/components/console/research/Rese…
info Commented-code block (5 lines) in frontend/src/pages/console/ConsoleProjectDeta…
info Commented-code block (6 lines) in frontend/src/redesign/console/research/Resear…
info Commented-code block (5 lines) in frontend/src/redesign/console/research/Resear…
info Commented-code block (5 lines) in frontend/src/redesign/console/canvas/canvasMo…
info Commented-code block (9 lines) in backend/main.py:7
info Commented-code block (7 lines) in backend/api/projects.py:313
info Commented-code block (6 lines) in backend/scripts/migrate_v3_rename.py:50
info Commented-code block (7 lines) in backend/tasks/output_tasks.py:277
info Commented-code block (6 lines) in backend/agents/converter_agent.py:697

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

info `truncate` class without `title=` for hover reveal — frontend/src/components/sy…
high FastAPI PUT `update_embedding_config` without auth dependency — backend/api/age… backend/api/agent_settings.py:421
high FastAPI DELETE `reset_embedding_config` without auth dependency — backend/api/a… backend/api/agent_settings.py:438
high FastAPI PUT `update_rerank_config` without auth dependency — backend/api/agent_… backend/api/agent_settings.py:455
high FastAPI DELETE `reset_rerank_config` without auth dependency — backend/api/agen… backend/api/agent_settings.py:471

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/0391a7dd-bc23-4b84-8026-e6a384c31474/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0391a7dd-bc23-4b84-8026-e6a384c31474/

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.