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.

wazionapps/nexo

https://github.com/wazionapps/nexo · scanned 2026-06-16 00:56 UTC (2 months, 1 week ago)

374 raw signals (0 security + 374 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 13 Medium 43 Low 197 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 359 Crowd 0 Layer: Software 25 Frontend 2 Hardware 3 Security 18 Cicd 3 Quality 258 Api 50

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

5 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 7 findings

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.

7 matching findings on this repo

low Old/deprecated-named symbol `orig_legacy` in tests/test_drive.py:403
low Old/deprecated-named symbol `sidecar_legacy` in tests/test_hook_runs_compact_si…
low Old/deprecated-named symbol `_canonical_supersedes_legacy` in src/cognitive_pat…
low Old/deprecated-named symbol `_brain_legacy` in src/calibration_migration.py:347
low Old/deprecated-named symbol `_load_legacy` in src/scripts/nexo-email-migrate-co…
low Old/deprecated-named symbol `sidecar_legacy` in src/hooks/compact_session_resol…
low Old/deprecated-named symbol `latest_legacy` in src/plugins/schedule.py:121

View all legacy markers findings →

Commented-out code 104 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 (5 lines) in tests/test_v78_compaction_continuity.py:121
info Commented-code block (11 lines) in tests/test_deep_sleep_rewrite.py:72
info Commented-code block (6 lines) in tests/test_workflow.py:26
info Commented-code block (5 lines) in tests/test_lifecycle_events.py:168
info Commented-code block (5 lines) in tests/test_cli_scripts.py:844
info Commented-code block (7 lines) in tests/test_auto_close_sessions_protocol.py:17
info Commented-code block (6 lines) in tests/test_resolution_cache.py:383
info Commented-code block (7 lines) in tests/test_personal_scripts_enabled.py:24
info Commented-code block (7 lines) in tests/test_deep_sleep_apply.py:26
info Commented-code block (7 lines) in tests/test_system_catalog_discoverability.py:…
info Commented-code block (5 lines) in tests/test_resolution_cache_composite_ids.py:…
info Commented-code block (5 lines) in tests/test_client_sync.py:1247

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

info Commented-code block (9 lines) in src/email_config.py:111
low Old/deprecated-named symbol `_load_legacy` in src/scripts/nexo-email-migrate-co…
info Commented-code block (6 lines) in src/scripts/nexo-email-migrate-config.py:2

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/cf21a208-8b98-42db-a611-fa0240a79b8a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cf21a208-8b98-42db-a611-fa0240a79b8a/

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.