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.

synaptent/aragora

https://github.com/synaptent/aragora · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

2853 raw signals (93 security + 2760 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 2344 actionable findings from 2 signal sources. 713 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 · 2335 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 13 High 57 Medium 334 Low 1490 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 2335 Crowd 0 Layer: Quality 1804 Security 115 Cicd 4 Software 1 Api 1 Frontend 401 Data 1 Network 11 Hardware 6

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

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

low Very large file: tests/handlers/connectors/test_legacy.py (2291 lines)
low Old/deprecated-named symbol `unencrypted_legacy` in tests/security/test_encrypt…
low Old/deprecated-named symbol `test_missing_maps_legacy` in tests/client/test_deb…
low Old/deprecated-named symbol `is_legacy` in tests/integration/test_handler_regis…
low Old/deprecated-named symbol `test_explicit_mode_overrides_legacy` in tests/conf…
low Old/deprecated-named symbol `_seed_legacy` in tests/analytics/test_benchmarking…
low Old/deprecated-named symbol `is_legacy` in tests/connectors/enterprise/database…
low Old/deprecated-named symbol `test_resolve_default_roots_picks_canonical_then_le…
low Old/deprecated-named symbol `test_implement_phase_without_executor_uses_legacy`…
low Old/deprecated-named symbol `test_gate_error_falls_back_to_legacy` in tests/nom…
low Old/deprecated-named symbol `test_register_legacy` in tests/audit/test_audit_re…
low Old/deprecated-named symbol `test_get_summary_with_legacy` in tests/billing/tes…

View all legacy markers findings →

Commented-out code 224 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 (6 lines) in tests/test_phase_recovery.py:278
info Commented-code block (5 lines) in tests/routing/test_provider_routing.py:267
info Commented-code block (9 lines) in tests/integration/test_billing_flow.py:679
info Commented-code block (6 lines) in tests/integration/test_handler_registration.p…
info Commented-code block (6 lines) in tests/integration/test_handler_registry_impor…
info Commented-code block (5 lines) in tests/integration/test_debate_smoke.py:96
info Commented-code block (8 lines) in tests/triage/test_auto_handle_calibration.py:…
info Commented-code block (5 lines) in tests/swarm/test_swarm_config.py:348
info Commented-code block (5 lines) in tests/swarm/test_worker_contract_drift_alignm…
info Commented-code block (7 lines) in tests/review/test_protocol.py:331
info Commented-code block (5 lines) in tests/review/test_alert.py:717
info Commented-code block (5 lines) in tests/review/test_policy.py:116

View all commented-out code findings →

Config drift 28 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 Icon-only button without accessible name — aragora/live/src/components/control-…
medium Insecure pattern 'node_child_process' in aragora/live/next.config.js:13 aragora/live/next.config.js:13
low Very large file: tests/debate/test_arena_config.py (1582 lines)
low Very large file: tests/debate/test_orchestrator_config_merge.py (1514 lines)
low Very large file: tests/handlers/agents/test_config.py (1743 lines)
low Very large file: tests/handlers/_oauth/test_config.py (1387 lines)
low Very large file: tests/storage/test_webhook_config_store.py (2231 lines)
low Very large file: aragora/storage/webhook_config_store.py (1487 lines)
medium Runtime service client appears to use placeholder configuration
low Old/deprecated-named symbol `test_get_registered_returns_copy` in tests/test_re…
info Commented-code block (5 lines) in tests/swarm/test_swarm_config.py:348
low Old/deprecated-named symbol `core_deprecated` in tests/config/test_feature_flag…

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/9887efad-bbcd-46cd-8a2a-2657f76cd81c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9887efad-bbcd-46cd-8a2a-2657f76cd81c/

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.