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.

whiteguo233/OpenBiliClaw

https://github.com/whiteguo233/OpenBiliClaw · scanned 2026-06-16 00:57 UTC (2 months, 1 week ago)

287 raw signals (0 security + 287 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 256 actionable findings from 1 signal source. 31 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 · 256 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 7 Medium 32 Low 138 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 256 Crowd 0 Layer: Software 17 Frontend 8 Hardware 3 Security 19 Cicd 3 Quality 152 Api 54

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 3 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 13 places
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

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 Old/deprecated-named symbol `BV_legacy` in tests/test_franchise_key_e2e.py:74
low Old/deprecated-named symbol `test_migrate_noop_when_nothing_legacy` in tests/te…
low Old/deprecated-named symbol `from_legacy` in src/openbiliclaw/soul/profile_buil…
low Old/deprecated-named symbol `from_legacy` in src/openbiliclaw/soul/engine.py:301
low Old/deprecated-named symbol `from_legacy` in src/openbiliclaw/soul/profile.py:6…
low Old/deprecated-named symbol `embedding_cache_legacy` in src/openbiliclaw/llm/em…

View all legacy markers findings →

Commented-out code 77 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 tests/test_storage.py:502
info Commented-code block (5 lines) in tests/test_llm_prompts.py:457
info Commented-code block (5 lines) in tests/test_x_client.py:44
info Commented-code block (5 lines) in tests/test_api_auth.py:674
info Commented-code block (9 lines) in tests/test_cli.py:2482
info Commented-code block (5 lines) in tests/test_e2e_multi_source_diversity.py:435
info Commented-code block (6 lines) in tests/test_trending_strategy.py:290
info Commented-code block (5 lines) in tests/test_refresh_runtime.py:1217
info Commented-code block (6 lines) in tests/test_llm_usage.py:332
info Commented-code block (6 lines) in scripts/agent_bootstrap.py:103
info Commented-code block (5 lines) in extension/tests/xhs-task-executor.test.ts:876
info Commented-code block (5 lines) in extension/tests/runtime-refresh-coalescing.te…

View all commented-out code findings →

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

4 matching findings on this repo

low Possibly dead Python function: llm_concurrency_from_config src/openbiliclaw/config.py:1196
low Very large file: tests/test_config.py (1966 lines)
low Very large file: src/openbiliclaw/config.py (1970 lines)
info Commented-code block (8 lines) in src/openbiliclaw/config.py:115

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/0ecdaa0e-b847-4b17-a37b-d6a788fd0806/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0ecdaa0e-b847-4b17-a37b-d6a788fd0806/

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.