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.

vamseeachanta/workspace-hub

https://github.com/vamseeachanta/workspace-hub · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

1643 raw signals (0 security + 1643 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 1584 actionable findings from 1 signal source. 59 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 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 `test_stage5_gate_migration_exemption_allows_legacy…
  • low Old/deprecated-named symbol `superseded_or_legacy` in tests/audits/test_online_…
  • low Old/deprecated-named symbol `expected_legacy` in tests/knowledge/test_engineeri…
  • low Old/deprecated-named symbol `should_rename_legacy` in pylib/charset_normalizer/…
View all legacy markers findings →
Commented-out code 44 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/operations/test_dispatch_lease.py:253
  • info Commented-code block (7 lines) in tests/readiness/test_collect_equality.py:561
  • info Commented-code block (5 lines) in tests/workstations/test_dispatch.py:146
  • info Commented-code block (6 lines) in tests/analysis/test_repo_architecture_scanner…
  • info Commented-code block (5 lines) in tests/strategic/test_strategic_score.py:126
  • info Commented-code block (7 lines) in tests/knowledge/test_naval_architecture_expan…
  • info Commented-code block (7 lines) in tests/knowledge/test_engineering_standards_as…
  • info Commented-code block (6 lines) in tests/knowledge/test_engineering_pipeline_exp…
  • info Commented-code block (5 lines) in tests/knowledge/test_engineering_riser_expans…
  • info Commented-code block (5 lines) in tests/knowledge/test_ocimf_tandem_no_raw_pdf_…
  • info Commented-code block (6 lines) in scripts/legal/redact-client-pii.py:49
  • info Commented-code block (6 lines) in scripts/operations/git_ref_lease.py:57
View all commented-out code findings →
Config drift 332 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 Stray `console.log` in TS/JS — _archive/modules/utilities/utils/config-validato…
  • low Stray `console.log` in TS/JS — examples/advanced-configuration.ts:9
  • medium Insecure pattern 'subprocess_shell_true' in config/ai-tools/provider-kanban.jso… config/ai-tools/provider-kanban.json:4444
  • medium Insecure pattern 'subprocess_shell_true' in config/ai-tools/provider-work-queue… config/ai-tools/provider-work-queue.json:1567
  • medium Agent authority lacks a verifier contract: _archive/modules/config/.mcp.json _archive/modules/config/.mcp.json
  • high Agent instruction/config may expose a secret: _archive/skills/automation/windmi… _archive/skills/automation/windmill/SKILL.md:73
  • high Agent instruction/config may expose a secret: _archive/skills/automation/n8n/SK… _archive/skills/automation/n8n/SKILL.md:978
  • high Agent instruction/config may expose a secret: _archive/skills/automation/active… _archive/skills/automation/activepieces/SKILL.md:77
  • high Agent instruction/config may expose a secret: _archive/skills/automation/airflo… _archive/skills/automation/airflow/SKILL.md:384
  • high Agent instruction/config may expose a secret: _archive/skills/automation/github… _archive/skills/automation/github-actions/SKILL.md:555
  • high Agent instruction/config may expose a secret: _archive/skills/devtools/docker/S… _archive/skills/devtools/docker/SKILL.md:325
  • high Agent instruction/config may expose a secret: _archive/skills/devtools/raycast-… _archive/skills/devtools/raycast-alfred/SKILL.md:807
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/63d7eb11-96f3-45af-9110-2ba8dda3f5ae/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/63d7eb11-96f3-45af-9110-2ba8dda3f5ae/

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.