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.

twobrains-technology/aja-agora

https://github.com/twobrains-technology/aja-agora · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

227 raw signals (30 security + 197 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 203 actionable findings from 2 signal sources. 64 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 · 194 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 6 Medium 28 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 194 Crowd 0 Layer: Quality 141 Security 20 Api 1 Frontend 36 Hardware 2 Cicd 3

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.

Commented-out code 119 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/helpers/fixture-discovery-adapter.ts:1
info Commented-code block (5 lines) in tests/eval/jornada-aja-agora.eval.test.ts:76
info Commented-code block (5 lines) in tests/eval/anthropic-availability.ts:3
info Commented-code block (7 lines) in tests/eval/assistant-flow.eval.test.ts:141
info Commented-code block (8 lines) in tests/eval/agent-flow.eval.test.ts:547
info Commented-code block (6 lines) in tests/eval/bevi-partner-offer-shape.eval.test…
info Commented-code block (6 lines) in tests/regression/migrate-guard.test.ts:3
info Commented-code block (8 lines) in tests/regression/agent-trajectory.test.ts:173
info Commented-code block (6 lines) in tests/e2e/specs/chat-scroll/scroll-intent.spe…
info Commented-code block (5 lines) in scripts/validate-eval-schema.mjs:4
info Commented-code block (5 lines) in scripts/migrate-guard.mjs:4
info Commented-code block (5 lines) in src/components/chat/message-list.test.tsx:1

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

info Commented-code block (5 lines) in src/lib/agent/qualify-config.ts:154

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/96b85fd3-4fc8-4563-8089-f06b2cf2c60d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/96b85fd3-4fc8-4563-8089-f06b2cf2c60d/

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.