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.

siran/egpt

https://github.com/siran/egpt · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

212 raw signals (0 security + 212 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 212 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 212 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 34 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 212 Crowd 0 Layer: Frontend 1 Network 2 Security 24 Cicd 1 Quality 184

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 169 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 dispatch.mjs:88
info Commented-code block (5 lines) in conversations-state.mjs:4
info Commented-code block (6 lines) in author-emoji.mjs:4
info Commented-code block (7 lines) in egpt-daemon.mjs:7
info Commented-code block (9 lines) in egpt.mjs:83
info Commented-code block (12 lines) in config/config-schema.mjs:25
info Commented-code block (6 lines) in config/brains/claude-sdk.mjs:3
info Commented-code block (10 lines) in config/brains/claude-code.mjs:1
info Commented-code block (5 lines) in config/brains/chatgpt-cdp.mjs:12
info Commented-code block (6 lines) in config/brains/llama.mjs:1
info Commented-code block (5 lines) in config/brains/codex.mjs:344
info Commented-code block (8 lines) in tests/claude-sdk-sandbox.test.mjs:1

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

medium Insecure pattern 'node_child_process' in config/brains/claude-code.mjs:20 config/brains/claude-code.mjs:20
medium Insecure pattern 'direct_innerhtml_assignment' in config/brains/chatgpt-cdp.mjs… config/brains/chatgpt-cdp.mjs:85
medium Insecure pattern 'direct_innerhtml_assignment' in config/brains/claude-cdp.mjs:… config/brains/claude-cdp.mjs:85
medium Insecure pattern 'node_child_process' in config/brains/codex.mjs:8 config/brains/codex.mjs:8
info Commented-code block (12 lines) in config/config-schema.mjs:25
info Commented-code block (6 lines) in config/brains/claude-sdk.mjs:3
info Commented-code block (10 lines) in config/brains/claude-code.mjs:1
info Commented-code block (5 lines) in config/brains/chatgpt-cdp.mjs:12
info Commented-code block (6 lines) in config/brains/llama.mjs:1
info Commented-code block (5 lines) in config/brains/codex.mjs:344
info Commented-code block (7 lines) in slash/config.mjs:3
info Commented-code block (8 lines) in src/config-validate.mjs:4

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/ed5a7287-aedd-4f0b-8fd1-1ac456953a63/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ed5a7287-aedd-4f0b-8fd1-1ac456953a63/

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.