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.

ruoso/a-conversa

https://github.com/ruoso/a-conversa · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

1187 raw signals (36 security + 1151 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 1092 actionable findings from 2 signal sources. 145 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 · 1082 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 5 Medium 46 Low 94 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 10 System graph 1082 Crowd 0 Layer: Quality 1040 Security 17 Frontend 15 Hardware 3 Cicd 4 Api 13

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 3 places repo-level
low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Commented-out code 936 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 playwright.config.ts:9
info Commented-code block (5 lines) in cucumber.cjs:9
info Commented-code block (8 lines) in eslint.config.js:6
info Commented-code block (9 lines) in vitest.config.ts:4
info Commented-code block (7 lines) in vitest.setup.ts:3
info Commented-code block (7 lines) in tests/vite-env.d.ts:4
info Commented-code block (9 lines) in tests/smoke/coherency-hint-kind-parity.test.t…
info Commented-code block (6 lines) in tests/smoke/dev-user-pool.test.ts:9
info Commented-code block (11 lines) in tests/smoke/wsStoreSeed.test.ts:4
info Commented-code block (9 lines) in tests/smoke/lint-migrations.test.ts:9
info Commented-code block (6 lines) in tests/smoke/hello.test.ts:1
info Commented-code block (6 lines) in tests/behavior/steps/backend-reference-permis…

View all commented-out code findings →

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

critical Insecure pattern 'private_key_in_repo' in infra/authelia/configuration.yml:174 infra/authelia/configuration.yml:174
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in playwright.config.ts:9
info Commented-code block (8 lines) in eslint.config.js:6
info Commented-code block (9 lines) in vitest.config.ts:4
info Commented-code block (11 lines) in tests/behavior/steps/backend-oauth-config.st…
info Commented-code block (8 lines) in apps/participant/vite.config.ts:3
info Commented-code block (8 lines) in apps/test-mode/vite.config.ts:3
info Commented-code block (6 lines) in apps/moderator/vite.config.ts:48
info Commented-code block (8 lines) in apps/audience/vite.config.ts:3
info Commented-code block (7 lines) in apps/server/src/auth/config.ts:11
info Commented-code block (22 lines) in apps/server/src/auth/config.test.ts:11

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/4f25cc9f-c821-43e2-8f3d-d2f742c6eef7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4f25cc9f-c821-43e2-8f3d-d2f742c6eef7/

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.