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.

thinkwork-ai/thinkwork

https://github.com/thinkwork-ai/thinkwork · scanned 2026-06-16 00:36 UTC (2 months, 2 weeks ago)

914 raw signals (0 security + 914 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 900 actionable findings from 1 signal source. 14 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 1 finding
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.
1 matching finding on this repo
  • low Near-duplicate function bodies in 2 places repo-level
View all duplicates & near-duplicates findings →
Legacy markers 5 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.
5 matching findings on this repo
  • low Old/deprecated-named symbol `totalLegacy` in packages/api/scripts/wipe-external…
  • low Old/deprecated-named symbol `nLegacy` in packages/api/src/lib/__tests__/workspa…
  • low Old/deprecated-named symbol `withLegacy` in packages/api/src/lib/workspace-rend…
  • low Old/deprecated-named symbol `tp_legacy` in packages/api/src/graphql/resolvers/t…
  • low Old/deprecated-named symbol `tp_legacy` in packages/api/src/graphql/resolvers/t…
View all legacy markers findings →
Commented-out code 300 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 apps/cli/__tests__/registration-smoke.test.ts…
  • info Commented-code block (6 lines) in apps/cli/__tests__/terraform-sandbox-host-fix…
  • info Commented-code block (8 lines) in apps/cli/src/commands/login.ts:680
  • info Commented-code block (5 lines) in apps/cli/src/commands/deploy.ts:464
  • info Commented-code block (5 lines) in apps/cli/src/commands/mcp.ts:538
  • info Commented-code block (8 lines) in apps/desktop/electron.vite.config.ts:31
  • info Commented-code block (5 lines) in apps/desktop/src/main/protocol.ts:114
  • info Commented-code block (5 lines) in apps/desktop/src/main/window.ts:70
  • info Commented-code block (12 lines) in apps/mobile/metro.config.js:24
  • info Commented-code block (7 lines) in apps/mobile/scripts/generate-brand-assets.mjs…
  • info Commented-code block (7 lines) in apps/mobile/components/threads/ActivityTimeli…
  • info Commented-code block (9 lines) in apps/mobile/components/wiki/graph/WikiGraphVi…
View all commented-out code findings →
Config drift 21 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.
12 matching findings on this repo
  • low Possibly dead Python function: configure_bank packages/agentcore/agent-container/hindsight_clie…
  • low Stray `console.log` in TS/JS — apps/cli/src/commands/config.ts:84
  • info TODO/FIXME marker in shipping code — apps/mobile/app/skills/configure.tsx:38
  • info `truncate` class without `title=` for hover reveal — apps/web/src/components/se…
  • info `truncate` class without `title=` for hover reveal — apps/web/src/components/ro…
  • low Stray `console.log` in TS/JS — packages/api/src/__tests__/workflow-config-e2e.s…
  • low Stray `console.log` in TS/JS — packages/api/src/lib/mcp-configs.ts:263
  • low Stray `console.log` in TS/JS — packages/api/src/lib/resolve-agent-runtime-confi…
  • medium Insecure pattern 'cors_wildcard' in packages/api/src/handlers/agents-runtime-co… packages/api/src/handlers/agents-runtime-config.ts:41
  • low Node manifest has dependencies but no lockfile: packages/pricing-config/package… packages/pricing-config/package.json
  • low Node manifest has dependencies but no lockfile: packages/runtime-config/package… packages/runtime-config/package.json
  • info Commented-code block (8 lines) in apps/desktop/electron.vite.config.ts:31
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/62aa8858-5e12-4e63-b5c3-182d4d043989/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/62aa8858-5e12-4e63-b5c3-182d4d043989/

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.