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.

rizom-ai/brains

https://github.com/rizom-ai/brains · scanned 2026-06-15 23:53 UTC (2 months, 3 weeks ago)

325 raw signals (0 security + 325 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 302 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

100.0% cov · 302 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 14 Medium 108 Low 150 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 302 Crowd 0 Layer: Frontend 55 Network 13 Hardware 3 Security 30 Cicd 4 Quality 180 Api 17

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `nLegacy` in entities/topics/test/atproto-projectio…

View all legacy markers findings →

Commented-out code 20 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 (7 lines) in brains/relay/src/index.ts:198
info Commented-code block (12 lines) in shared/site-engine/test/route-registry.test.…
info Commented-code block (5 lines) in shared/ui-library/src/OgCard.tsx:8
info Commented-code block (6 lines) in shared/ui-library/src/markdown-html.ts:85
info Commented-code block (7 lines) in shared/deploy-support/src/index.ts:209
info Commented-code block (6 lines) in interfaces/webserver/test/server-manager.test…
info Commented-code block (5 lines) in interfaces/webserver/src/webserver-interface.…
info Commented-code block (5 lines) in packages/brain-cli/scripts/entrypoint.ts:71
info Commented-code block (5 lines) in packages/brain-cli/scripts/build.ts:120
info Commented-code block (9 lines) in packages/brain-cli/src/lib/env-schema.ts:11
info Commented-code block (5 lines) in shell/ai-evaluation/test/per-model-git-remote…
info Commented-code block (6 lines) in shell/job-queue/src/job-queue-repository.ts:2…

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

low Stray `console.log` in TS/JS — shell/ai-evaluation/src/eval-config-loader.ts:66
low Node manifest has dependencies but no lockfile: shared/eslint-config/package.js… shared/eslint-config/package.json
low Node manifest has dependencies but no lockfile: shared/cms-config/package.json shared/cms-config/package.json

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/5538f4d1-b828-46f8-9dd1-95327ec4340f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5538f4d1-b828-46f8-9dd1-95327ec4340f/

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.