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.
Sign up free Scan another repo

syndicalt/zaxy

https://github.com/syndicalt/zaxy · scanned 2026-06-16 00:28 UTC (2 months, 2 weeks ago)

183 raw signals (0 security + 183 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
56.3
/100
Security checks
56
0 findings
System graph
56
88.9% cov · 156 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 2 Medium 18 Low 126 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 156 Crowd 0 Layer: Software 22 Network 1 Hardware 2 Frontend 1 Security 7 Cicd 3 Quality 120
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 56.3/100 with 88.9% coverage. It contains 10035 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 183 findings — concentrated in quality (134), software (24), cicd (12). Risk profile is high: 3 critical, 2 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 148 of 156 actionable findings. 183 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in scripts/setup.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/setup.sh:43
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in zaxy_benchmarks/longmembench.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 891, 904
zaxy_benchmarks/longmembench.py:891, 904 (2 hits)
high System graph security security conf 1.00 Insecure pattern 'eval_used' in site/docs/research/codebase-review-2026-06-09.html:467
Found a known-risky pattern (eval_used). Review and replace if possible.
site/docs/research/codebase-review-2026-06-09.html:467 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in site/docs/research/codebase-review-2026-06-09.html:467
Found a known-risky pattern (exec_used). Review and replace if possible.
site/docs/research/codebase-review-2026-06-09.html:467 Exec used
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
codecov/codecov-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/ci.yml:60
.github/workflows/publish.yml:41
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/pages.yml
.github/workflows/publish-mcp.yml
.github/workflows/publish.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/docs/research/codebase-review-2026-06-09.html:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/docs/research/codebase-review-2026-06-09.html:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/docs/superpowers/plans/2026-06-09-codebase-review-high-value-remediation.html:156
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/docs/superpowers/plans/2026-06-09-codebase-review-high-value-remediation.html:156 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in site/docs/research/codebase-review-2026-06-09.html:38
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
site/docs/research/codebase-review-2026-06-09.html:38 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/check-backend-shootout.py:1340
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/check-state-recovery-benchmark.py:138
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/generate-release-media.py:182
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/zaxy/capture_manager.py:75
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/zaxy/cli/evaluation.py:1417
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/zaxy/coordination_git.py:148
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/zaxy/release.py:1157
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — zaxy_benchmarks/harvey_lab_benchmark.py:902
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — zaxy_benchmarks/longmembench.py:437
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — zaxy_benchmarks/rc_benchmark_freeze.py:951
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 21 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/release-check.sh Ports
low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CODEX_HOME`, `HERMES_HOME`, `OPENAI_API_KEY`, `PATH`, `RETRIEVAL_PROFILE`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 41 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.13-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 3, 24
Dockerfile:3, 24 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 7 locations
.github/workflows/ci.yml:19, 43, 72, 95 (4 hits)
.github/workflows/publish.yml:24, 27 (2 hits)
.github/workflows/pages.yml:47
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: zaxy_benchmarks/coordination_benchmark.py:to_dict, zaxy_benchmarks/coordination_benchmark.py:to_dict, zaxy_benchmarks/coordination_benchmark.py:to_dict, zaxy_benchmarks/coordination_benchmark.py:to_dict This is *the* AI-coder failure mode (4× more du…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 14 places
Functions with the same first-5-line body hash: zaxy_benchmarks/live_benchmark.py:query, zaxy_benchmarks/live_benchmark.py:query_async, zaxy_benchmarks/live_benchmark.py:query, zaxy_benchmarks/live_benchmark.py:query This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — se…
duplicatesduplication
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/backend-shootout.py:observe, scripts/backend-shootout.py:observe This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: zaxy_benchmarks/coordination_benchmark.py:from_dict, zaxy_benchmarks/coordination_benchmark.py:from_dict, zaxy_benchmarks/coordination_benchmark.py:from_dict This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://j…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/zaxy/embedded_graph_store.py:matrix_bytes, src/zaxy/embedded_graph_store.py:matrix_bytes, src/zaxy/embedded_graph_store.py:matrix_bytes, src/zaxy/embedded_graph_store.py:matrix_bytes This is *the* AI-coder failure mode (4× more duplication in vib…
duplicatesduplication
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: src/zaxy/query.py:rerank, src/zaxy/query.py:rerank, src/zaxy/query.py:rerank, src/zaxy/query.py:rerank This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they…
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `000_old` in tests/test_schema_migrations.py:47
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_extract_skill_deprecated` in src/zaxy/extract.py:647
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accepted_unused` in tests/test_coordination.py:236
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `coordination_proof_packet_v1` in src/zaxy/coordination.py:641
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `coordinationbench_synthesis_artifact_v1` in src/zaxy/coordinationbench_adapter.py:348
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deterministic_episode_segment_v1` in src/zaxy/consolidation_pipeline.py:228
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deterministic_segment_summary_v1` in tests/test_consolidation_pipeline.py:150
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deterministic_token_overlap_v1` in src/zaxy/core.py:1016
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deterministic_token_overlap_v1` in tests/test_metacognition.py:61
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `event_segment_cluster_v1` in tests/test_causal_benchmark.py:501
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `event_segment_cluster_v1` in tests/test_consolidation.py:27
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `evidence_program_v1` in src/zaxy/evidence_program.py:126
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `evidence_program_v1` in tests/test_evidence_program.py:36
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `explicit_outcome_citation_v1` in tests/test_causal.py:118
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `explicit_outcome_citation_v1` in tests/test_causal_checkout.py:23
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `explicit_outcome_citation_v1` in tests/test_mcp.py:706
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `explicit_outcome_explanation_v1` in tests/test_latticedb_store.py:178
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lexical_overlap_v1` in tests/test_graph.py:527
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/zaxy/cli/workspace.py:1008
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/zaxy/retrieval_profile.py:151
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in tests/test_event.py:93
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in tests/test_extract.py:114
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `slot_plan_v1` in src/zaxy/retrieval_plan/foundations.py:403
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `slot_plan_v1` in tests/test_synthesis_artifact.py:63
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `synthesis_artifact_v1` in src/zaxy/synthesis_artifact.py:18
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `synthesis_packet_v1` in src/zaxy/retrieval_plan/bundles.py:1680
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `synthesis_packet_v1` in tests/test_retrieval_plan.py:508
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `synthesis_packet_v1` in tests/test_synthesis_packet.py:263
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in src/zaxy/inference.py:17
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_checkout.py:387
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_cli.py:2343
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_core.py:597
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_inference.py:67
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_pggraph_store.py:515
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `task_completed_decision_citation_v1` in tests/test_query.py:864
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_embedded_store_connect_migration_never_overwrites_existing_backup` in tests/test_embedded_graph_store.py:4037
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_run_doctor_reports_leftover_pre_ladybug_backup` in tests/test_doctor.py:768
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `write_v1` in src/zaxy/event.py:293
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: aggregate_candidate_lines
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/evidence_candidates.py:1801
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/extract.py:103
low System graph software Dead code conf 1.00 Possibly dead Python function: default_fabric_factory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/adapters/_common.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: do_DELETE
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2668
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2622
low System graph software Dead code conf 1.00 Possibly dead Python function: do_PATCH
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2665
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2639
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/packet_analyzer.py:323
low System graph software Dead code conf 1.00 Possibly dead Python function: do_PUT
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2662
low System graph software Dead code conf 1.00 Possibly dead Python function: empty_recall_candidate_set
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/recall.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: eventloom_log
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/config.py:620
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/dashboard.py:2671
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/packet_analyzer.py:338
low System graph software Dead code conf 1.00 Possibly dead Python function: model_post_init
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/config.py:547
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: reject_constant
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
scripts/backend-shootout.py:739
scripts/build-backend-shootout-workload.py:74
scripts/check-backend-shootout.py:566
low System graph software Dead code conf 1.00 Possibly dead Python function: socket_reader
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/mcp_server.py:4204
low System graph software Dead code conf 1.00 Possibly dead Python function: socket_writer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/mcp_server.py:4217
low System graph software Dead code conf 1.00 Possibly dead Python function: stash_code
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build-site-docs.py:353
low System graph software Dead code conf 1.00 Possibly dead Python function: write_hypothesis
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reports/archive/benchmarks/longmembench-adapter-kit/zaxy_longmembench_runner.py:14
low System graph software Dead code conf 1.00 Possibly dead Python function: zaxy_crewai_coordination_step
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/adapters/crewai.py:304
low System graph software Dead code conf 1.00 Possibly dead Python function: zaxy_crewai_memory_checkout_step
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/adapters/crewai.py:288
low System graph software Dead code conf 1.00 Possibly dead Python function: zaxy_crewai_memory_step
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/zaxy/adapters/crewai.py:262
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — src/zaxy/packet_analyzer.py:338
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Complexity conf 1.00 Very large file: scripts/check-backend-shootout.py (1570 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/associative_memory.py (2292 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/checkout.py (2053 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/cli/benchmarks.py (1637 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/cli/evaluation.py (1424 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/cli/runtime.py (1407 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/cli/serving.py (1533 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/cli/workspace.py (1636 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/coordination.py (2307 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/core.py (5372 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/dashboard.py (2711 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/embedded_graph_store.py (2847 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/evidence_candidates.py (1803 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/extract.py (3594 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/graph.py (1582 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/mcp_server.py (4517 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/pggraph_store.py (1295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/query.py (1917 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/release.py (1547 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/bundles.py (1777 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/duration_evidence.py (1610 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/fact_queries.py (1574 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/foundations.py (1651 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/ordering.py (1624 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/retrieval_plan/scalars.py (1572 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/synthesis/evidence_rows.py (1519 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/synthesis/labels.py (1509 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/synthesis/ledgers.py (1603 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/zaxy/synthesis/operations.py (1544 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_backend_shootout.py (6310 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_checkout.py (1972 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_cli.py (8387 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_coordination.py (1478 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_coordination_benchmark.py (1446 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_core.py (4794 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_dashboard.py (1728 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_docs_site.py (1334 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_embedded_graph_store.py (4214 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_extract.py (2868 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_graph.py (1706 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_harvey_lab_benchmark.py (6841 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_live_benchmark.py (8407 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_longmembench.py (1821 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_mcp.py (4609 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_onboarding.py (1575 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_packaging.py (6089 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_query.py (2977 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_retrieval_plan.py (4762 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_synthesis.py (2905 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: zaxy_benchmarks/coordination_benchmark.py (1905 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: zaxy_benchmarks/harvey_lab_benchmark.py (4694 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: zaxy_benchmarks/live_benchmark.py (4084 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: zaxy_benchmarks/longmembench.py (3319 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/4cba3cd5-77c5-46b1-9f0b-6f1a71d83858/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4cba3cd5-77c5-46b1-9f0b-6f1a71d83858/

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.