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.

wangbinquan/agent-workflow

https://github.com/wangbinquan/agent-workflow · scanned 2026-06-16 00:54 UTC (2 months, 1 week ago)

1142 raw signals (0 security + 1142 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 11 Medium 63 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1094 Crowd 0 Layer: Frontend 10 Security 40 Cicd 3 Quality 980 Api 61

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

7 matching findings on this repo

low Old/deprecated-named symbol `s_legacy` in packages/frontend/tests/clarify-list-…
low Old/deprecated-named symbol `clarify_legacy` in packages/frontend/tests/homepag…
low Old/deprecated-named symbol `clarify_legacy` in packages/frontend/tests/inbox-d…
low Old/deprecated-named symbol `isLegacy` in packages/frontend/src/components/Attr…
low Old/deprecated-named symbol `hasLegacy` in packages/shared/src/schemas/task.ts:…
low Old/deprecated-named symbol `clarify_legacy` in packages/backend/tests/clarify-…
low Old/deprecated-named symbol `idLegacy` in packages/backend/tests/migration-0022…

View all legacy markers findings →

Commented-out code 916 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 (17 lines) in playwright.config.ts:3
info Commented-code block (8 lines) in tests/perf/run.ts:16
info Commented-code block (5 lines) in tests/perf/diff.ts:3
info Commented-code block (10 lines) in scripts/build-binary.ts:4
info Commented-code block (9 lines) in scripts/record-opencode.ts:6
info Commented-code block (7 lines) in packages/frontend/vite.config.ts:11
info Commented-code block (6 lines) in packages/frontend/tests/task-detail-page-tabs…
info Commented-code block (9 lines) in packages/frontend/tests/canvas-review-output-…
info Commented-code block (9 lines) in packages/frontend/tests/injected-memories-car…
info Commented-code block (10 lines) in packages/frontend/tests/review-detail-bubble…
info Commented-code block (5 lines) in packages/frontend/tests/launch-repo-source.te…
info Commented-code block (6 lines) in packages/frontend/tests/prompt-history-sort.t…

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

low Stray `console.log` in TS/JS — packages/frontend/vite.config.ts:65
info Commented-code block (17 lines) in playwright.config.ts:3
info Commented-code block (7 lines) in packages/frontend/vite.config.ts:11
info Commented-code block (6 lines) in packages/shared/tests/config-rfc048.test.ts:3
info Commented-code block (7 lines) in packages/shared/tests/compat-config-versions.…
info Commented-code block (6 lines) in packages/backend/tests/runner-build-inline-co…
low Unused endpoint: GET /api/config
low Unused endpoint: USE /api/config
low Unused endpoint: USE /api/config/*
low Unused endpoint: PUT /api/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/b620e3af-463f-4d0e-aab2-81e9c1d42488/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b620e3af-463f-4d0e-aab2-81e9c1d42488/

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.