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.

trezero/cortex

https://github.com/trezero/cortex · scanned 2026-06-16 00:42 UTC (2 months, 1 week ago)

345 raw signals (0 security + 345 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 308 actionable findings from 1 signal source. 37 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 · 308 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 110 Medium 36 Low 110 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 308 Crowd 0 Layer: Software 25 Frontend 53 Network 3 Hardware 3 Security 107 Cicd 3 Quality 53 Api 61

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 2 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.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Commented-out code 9 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/`.

9 matching findings on this repo

info Commented-code block (8 lines) in cortex-ui/src/components/settings/RAGSettings…
info Commented-code block (5 lines) in cortex-ui/src/features/agent-work-orders/stat…
info Commented-code block (5 lines) in cortex-ui/src/features/shared/api/apiClient.t…
info Commented-code block (5 lines) in cortex-ui/src/features/shared/api/tests/apiCl…
info Commented-code block (6 lines) in python/src/server/config/config.py:147
info Commented-code block (5 lines) in python/src/server/api_routes/knowledge_api.py…
info Commented-code block (6 lines) in python/src/server/services/credential_service…
info Commented-code block (6 lines) in python/src/server/services/crawling/helpers/u…
info Commented-code block (35 lines) in python/src/server/services/ollama/model_disc…

View all commented-out code findings →

Config drift 12 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 Stray `console.log` in TS/JS — cortex-ui/vite.config.ts:40
high Insecure pattern 'exec_used' in cortex-ui/vite.config.ts:74 cortex-ui/vite.config.ts:74
medium Insecure pattern 'node_child_process' in cortex-ui/vite.config.ts:6 cortex-ui/vite.config.ts:6
medium Insecure pattern 'cors_wildcard' in cortex-ui/vite.config.ts:69 cortex-ui/vite.config.ts:69
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:274
high Agent instruction/config may expose a secret: AGENTS.md AGENTS.md:196
high Agent instruction/config may expose a secret: postmanSkill/SKILL.md postmanSkill/SKILL.md:137
high Agent instruction/config may expose a secret: .claude/commands/init-project.md .claude/commands/init-project.md:53
high Agent instruction/config may expose a secret: .claude/agents/library-researcher… .claude/agents/library-researcher.md:62
info Commented-code block (6 lines) in python/src/server/config/config.py:147
high Dangling fetch: POST /api/providers/validate (cortex-ui/src/components/settings…
low Unused endpoint: GET /config

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/01c6bb35-20e7-45b4-beec-a55a0a966855/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01c6bb35-20e7-45b4-beec-a55a0a966855/

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.