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.

davistroy/open-brain

https://github.com/davistroy/open-brain · scanned 2026-06-17 01:54 UTC (1 month, 1 week ago)

580 raw signals (0 security + 580 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -35.9 (diff) · 523 actionable findings from 1 signal source. 57 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 · 523 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 286 Medium 47 Low 97 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 523 Crowd 0 Layer: Software 8 Frontend 41 Network 5 Hardware 7 Security 16 Cicd 3 Quality 110 Api 333

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 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 →

Commented-out code 58 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 reference/handoff/open-brain-cloudscape-desig…
info Commented-code block (5 lines) in packages/workers/src/main.ts:104
info Commented-code block (5 lines) in packages/workers/src/scheduler.ts:424
info Commented-code block (5 lines) in packages/workers/src/jobs/ingest-process.ts:18
info Commented-code block (5 lines) in packages/workers/src/jobs/budget-check.ts:190
info Commented-code block (5 lines) in packages/workers/src/jobs/ingestion-worker.ts…
info Commented-code block (5 lines) in packages/workers/src/lib/entity-resolver.ts:39
info Commented-code block (5 lines) in packages/workers/src/skills/pipeline-health-q…
info Commented-code block (6 lines) in packages/workers/src/skills/email-compose.ts:…
info Commented-code block (9 lines) in packages/workers/src/skills/refine-brief.ts:2…
info Commented-code block (5 lines) in packages/workers/src/skills/morning-brief-que…
info Commented-code block (6 lines) in packages/workers/src/__tests__/email-classify…

View all commented-out code findings →

Config drift 13 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

info `truncate` class without `title=` for hover reveal — packages/web-next/componen…
critical Possible secret in packages/core-api/src/__tests__/config-routes.test.ts packages/core-api/src/__tests__/config-routes.tes…:225
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in packages/web-next/lib/api/config.ts:34
high Dangling fetch: GET /config/integrations (packages/web-next/lib/api/config.ts:2…
high Dangling fetch: GET /triggers (packages/web-next/lib/api/config.ts:55)
high Dangling fetch: POST /triggers (packages/web-next/lib/api/config.ts:64)
high Dangling fetch: GET /config/ai-routing (packages/web-next/lib/api/config.ts:91)
high Dangling fetch: POST /api/v1/admin/config/reload (packages/core-api/src/__tests…
high Dangling fetch: POST /api/v1/admin/config/reload (packages/core-api/src/__tests…
high Dangling fetch: POST /api/v1/admin/config/reload (packages/core-api/src/__tests…
low Unused endpoint: GET /api/v1/config/ai-routing

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/d9335ca7-3927-4c09-92b4-fd872e0490bd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d9335ca7-3927-4c09-92b4-fd872e0490bd/

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.