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.

backspring-labs/squad-ops

https://github.com/backspring-labs/squad-ops · scanned 2026-06-17 01:37 UTC (1 month, 2 weeks ago)

130 raw signals (0 security + 130 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -13.4 (diff) · 107 actionable findings from 1 signal source. 23 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 107 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 23 Medium 12 Low 44 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 107 Crowd 0 Layer: Software 13 Hardware 6 Frontend 1 Security 30 Quality 57

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

View all duplicates & near-duplicates findings →

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

9 matching findings on this repo

low Old/deprecated-named symbol `v0_legacy` in adapters/capabilities/aci_executor.p…
low Old/deprecated-named symbol `test_missing_task_index_falls_back_to_legacy` in t…
low Old/deprecated-named symbol `hash_legacy` in tests/unit/cycles/test_legacy_pari…
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/api/runtime/__init__.p…
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/api/runtime/main.py:5
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/api/runtime/deps.py:4
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/core/lineage.py:7
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/tasks/types.py:11
low Old/deprecated-named symbol `_v0_legacy` in src/squadops/tasks/legacy_models.py…

View all legacy markers findings →

Commented-out code 21 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 adapters/cycles/distributed_flow_executor.py:…
info Commented-code block (5 lines) in tests/unit/cycles/test_postgres_cycle_registr…
info Commented-code block (6 lines) in tests/unit/cycles/test_acceptance_checks.py:4…
info Commented-code block (6 lines) in tests/unit/cycles/test_flow_executor.py:291
info Commented-code block (5 lines) in tests/unit/cycles/test_distributed_flow_execu…
info Commented-code block (5 lines) in tests/unit/capabilities/test_impl_handlers.py…
info Commented-code block (7 lines) in tests/unit/capabilities/test_planning_handler…
info Commented-code block (5 lines) in tests/unit/capabilities/handlers/test_typed_a…
info Commented-code block (5 lines) in src/squadops/cycles/plan_delta.py:32
info Commented-code block (5 lines) in src/squadops/cycles/task_plan.py:58
info Commented-code block (5 lines) in src/squadops/agents/entrypoint.py:690
info Commented-code block (6 lines) in src/squadops/agents/skills/qa/test_execution.…

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

critical Possible secret in config/profiles/dev.yaml config/profiles/dev.yaml:13
critical Possible secret in config/profiles/lab.yaml config/profiles/lab.yaml:17
critical Possible secret in config/profiles/local.yaml config/profiles/local.yaml:17
critical Possible secret in config/profiles/cloud.yaml config/profiles/cloud.yaml:17

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/14baa291-8323-4aa5-9949-0ddea526f395/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/14baa291-8323-4aa5-9949-0ddea526f395/

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.