grandamenium/cortextos

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.

49 of your 181 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.7s · analysis 29.73s · 6.5 MB · GitHub API rate-limit (preflight)

https://github.com/grandamenium/cortextos · scanned 2026-06-05 16:41 UTC (5 days ago) · 10 languages

552 raw signals (170 security + 382 graph) 12th percentile · Typescript · large (100-500K LoC) System graph score 86 (lower by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days ago · v2 · 293 actionable findings from 2 signal sources. 68 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 191 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	0.2	0.25	0.05
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	75.0	0.15	11.25
`code_quality`	44.0	0.10	4.40
Overall		1.00	63.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 38 Medium 39 Low 110 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 102 System graph 191 Crowd 0 Layer: Quality 105 Security 29 Software 93 Cicd 3 Api 1 Frontend 62

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

View all duplicates & near-duplicates findings →

Commented-out code 60 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 ecosystem.config.js:27
info Commented-code block (5 lines) in tests/integration/phase5-failure-modes.test.t…
info Commented-code block (7 lines) in tests/integration/multi-agent-crons.test.ts:73
info Commented-code block (5 lines) in tests/integration/phase5-audit.test.ts:222
info Commented-code block (5 lines) in tests/integration/phase2-backtesting.test.ts:…
info Commented-code block (5 lines) in tests/integration/phase5-performance.test.ts:…
info Commented-code block (13 lines) in tests/integration/phase5-e2e-simulation.test…
info Commented-code block (12 lines) in tests/integration/phase1-backtesting.test.ts…
info Commented-code block (5 lines) in tests/unit/pty/output-buffer.test.ts:83
info Commented-code block (5 lines) in tests/unit/telegram/api.test.ts:45
info Commented-code block (5 lines) in tests/unit/cli/bus-crons.test.ts:130
info Commented-code block (5 lines) in tests/unit/utils/allowed-roots.test.ts:225

View all commented-out code findings →

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

8 matching findings on this repo

low File has no detected symbols: ecosystem.config.js
low File has no detected symbols: playwright.config.ts
low File has no detected symbols: tsup.config.ts
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: src/cli/get-config.ts
low Stray `console.log` in TS/JS — src/cli/get-config.ts:72
info Commented-code block (7 lines) in ecosystem.config.js:27
info Commented-code block (6 lines) in dashboard/src/lib/config.ts:123

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/fe92d101-9133-494a-88fb-6b9c0f3458e0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fe92d101-9133-494a-88fb-6b9c0f3458e0/

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.