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

yannabadie/YGN-SAGE

https://github.com/yannabadie/YGN-SAGE · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

343 raw signals (0 security + 343 graph)

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

Complete repo analysis

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

JSON
Combined
49.2
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 295 findings
Critical
3
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 3 High 11 Medium 23 Low 153 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 295 Crowd 0 Layer: Software 23 Hardware 4 Frontend 1 Security 22 Cicd 4 Quality 232 Api 9
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 49.2/100 with 100.0% coverage. It contains 10417 nodes across 15 cross-layer flows, written primarily in mixed languages. Engine surfaced 343 findings — concentrated in quality (249), cicd (33), security (24). Risk profile is high: 5 critical, 11 high, 30 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 189 of 295 actionable findings. 343 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 security conf 1.00 Insecure pattern 'private_key_in_repo' in sage-python/src/sage/security/redaction.py:19
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
sage-python/src/sage/security/redaction.py:19 Private key in repo
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 7
docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:7 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 23
docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:23 (2 hits)
high System graph quality Integrity conf 1.00 Blocking `urllib.request.urlretrieve(...)` inside `async def download_pdf` — sage-discover/src/discover/ingestion.py:150
Sync I/O inside an async function blocks the event loop. While `urllib.request.urlretrieve(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await…
sage-discover/src/discover/ingestion.py:150 Sync io in asyncPerformance
high System graph security security conf 1.00 Insecure pattern 'eval_used' in sage-core/src/sandbox/validator.rs:242
Found a known-risky pattern (eval_used). Review and replace if possible.
sage-core/src/sandbox/validator.rs:242 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in sage-python/scripts/swebench_repair_and_eval_v16.py:173
Found a known-risky pattern (eval_used). Review and replace if possible.
sage-python/scripts/swebench_repair_and_eval_v16.py:173 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in sage-python/src/sage/bench/humaneval_data.json:1125
Found a known-risky pattern (eval_used). Review and replace if possible.
sage-python/src/sage/bench/humaneval_data.json:1125 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in sage-python/src/sage/topology/kg_rlvr.py:75
Found a known-risky pattern (eval_used). Review and replace if possible.
sage-python/src/sage/topology/kg_rlvr.py:75 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in sage-python/src/sage/topology/README.md:13
Found a known-risky pattern (eval_used). Review and replace if possible.
sage-python/src/sage/topology/README.md:13 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in sage-core/plugins/cpython-runner/app.py:68
Found a known-risky pattern (exec_used). Review and replace if possible.
sage-core/plugins/cpython-runner/app.py:68 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in sage-core/src/sandbox/validator.rs:235
Found a known-risky pattern (exec_used). Review and replace if possible.
sage-core/src/sandbox/validator.rs:235 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in sage-core/src/verification/smt.rs:1150
Found a known-risky pattern (exec_used). Review and replace if possible.
sage-core/src/verification/smt.rs:1150 Exec used
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in CLAUDE.md:10
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
CLAUDE.md:10 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in scripts/exocortex_ingest.py:50
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
scripts/exocortex_ingest.py:50 Tls verify false
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/static/js/chat.js:246
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/rules/meta-harness.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/rules/meta-harness.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.local.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.local.json VerificationClaude instruction
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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 8 locations
.github/workflows/wheels.yml:72, 116, 138, 272 (4 hits)
.github/workflows/release-test.yml:98, 143, 231 (3 hits)
.github/workflows/rust-core-coverage.yml:17
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/wheels.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/static/js/chat.js:73
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/static/js/chat.js:73 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/static/js/dashboard.js:424
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/static/js/dashboard.js:424 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/static/js/events.js:63
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/static/js/events.js:63 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/static/js/providers.js:100
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/static/js/providers.js:100 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/static/js/topology.js:84
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/static/js/topology.js:84 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in clients/pi-ygn-sage/src/index.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
clients/pi-ygn-sage/src/index.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:383
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:383 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:81
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:81 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in sage-python/src/sage/sandbox/manager.py:137
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
sage-python/src/sage/sandbox/manager.py:137 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — sage-discover/src/discover/ingestion.py:150
`urllib.request.urlretrieve(...)` 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 — sage-python/scripts/run_swebench_ablation.py:180
`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 — sage-python/scripts/swebench_parity_smoke.py:88
`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 — sage-python/src/sage/bench/swebench_ca_patch.py:218
`requests.get(...)` 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 — sage-python/src/sage/tools/meta.py:178
`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 115 placeholder/mock markers across 28 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 70 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CLAUDE_WRAPPER_LOG_DIR`, `CODEX_BIN`, `CONTEXT7`, `CONTEXT7_API_KEY`, `DEBUG`, `DEEP_SEEK_API_KEY`, `DOCKER_CONTEXT`, `DOCKER_HOST` + 62 more. 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 998 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 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.
Dockerfile:26 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:5 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 23 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/cache@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 23 locations
.github/workflows/ci.yml:41, 82, 137, 209, 298, 372, 434, 508 (8 hits)
.github/workflows/release-test.yml:93, 103, 151, 170, 191, 210, 217, 273 (8 hits)
.github/workflows/wheels.yml:67, 77, 250 (3 hits)
.github/workflows/latest-deps.yml:77, 86 (2 hits)
.github/workflows/doc-counters-coherence.yml:36
.github/workflows/rust-core-coverage.yml:34
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 14 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: external/meta-harness/reference_examples/terminal_bench_2/claude_wrapper.py:show, external/meta-harness/reference_examples/text_classification/claude_wrapper.py:show This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see h…
14 occurrences
repo-level (14 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: external/meta-harness/reference_examples/text_classification/inner_loop.py:predict_one, external/meta-harness/reference_examples/text_classification/inner_loop.py:predict_one, external/meta-harness/reference_examples/text_classification/inner_loop.py:…
5 occurrences
repo-level (5 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: sage-python/scripts/paired_run_diff.py:main, sage-python/scripts/diff_verifier_repair_ablation.py:main, sage-python/scripts/diff_fidelity_audit.py:main, sage-python/scripts/canary_pre_grader_gate.py:main This is *the* AI-coder failure mode (4× more d…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_run_legacy` in sage-python/src/sage/agent_loop_memory.py:3
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 `canary_pre_grader_gate_v1` in sage-python/scripts/canary_pre_grader_gate.py:289
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 `canary_pre_grader_gate_v1` in sage-python/tests/test_canary_pre_grader_gate.py:399
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 `cli_v1` in clients/pi-ygn-sage/src/index.ts:76
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 `cli_v1` in clients/pi-ygn-sage/test/contract.test.ts:37
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 `cli_v1` in clients/pi-ygn-sage/test/fixtures/backend-fixture.mjs:55
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 `cli_v1` in sage-python/src/sage/cli/run.py:316
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 `cli_v1` in sage-python/tests/test_sage_cli_jsonl.py:73
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 `days_old` in sage-discover/src/discover/frontier.py:113
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 `diff_fidelity_audit_v1` in sage-python/scripts/diff_fidelity_audit.py:300
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 `diff_verifier_repair_ablation_v1` in sage-python/scripts/diff_verifier_repair_ablation.py:298
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 `finalized_backup` in sage-python/src/sage/ops/a14_reset.py:154
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 `grpo_v2` in sage-python/src/sage/execution/__init__.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 `paired_run_diff_v1` in sage-python/scripts/paired_run_diff.py:177
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 `path_e_step3_v1` in sage-python/src/sage/bench/path_e_validate.py:434
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 `pipeline_fallback_legacy` in sage-python/tests/test_execution_path.py:4
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 `pipeline_v2` in docs/benchmarks/2026-05-11-provider-execution-witness-chain/reproduce.py:28
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 `pipeline_v2` in sage-python/src/sage/agent_loop.py:701
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 `pipeline_v2` in sage-python/src/sage/agent_loop_execution.py:349
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 `pipeline_v2` in sage-python/src/sage/boot.py:288
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 `pipeline_v2` in sage-python/src/sage/boot_providers.py:19
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 `pipeline_v2` in sage-python/src/sage/contracts/planner.py:179
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 `pipeline_v2` in sage-python/src/sage/llm/provider_pool.py:110
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 `pipeline_v2` in sage-python/src/sage/pipeline.py:2
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/__init__.py:1
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/assign_models.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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/bandit_attribution.py:190
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/classify.py:26
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/constructor.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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/costing.py:14
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/decompose.py:62
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/execute.py:25
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/learn.py:8
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/orchestrator.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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/runtime_events.py:19
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/select_topology.py:12
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 `pipeline_v2` in sage-python/src/sage/pipeline_v2/topology_helpers.py:4
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 `pipeline_v2` in sage-python/src/sage/providers/connector.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 `pipeline_v2` in sage-python/src/sage/topology/runner.py:25
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 `pipeline_v2` in sage-python/src/sage/topology_controller.py:563
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 `pipeline_v2` in sage-python/tests/observability/test_pipeline_spans.py:44
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 `pipeline_v2` in sage-python/tests/security/test_prompt_injection_pipeline.py:52
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 `pipeline_v2` in sage-python/tests/test_assigner_trace.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 `pipeline_v2` in sage-python/tests/test_e2e_campaign.py:168
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 `pipeline_v2` in sage-python/tests/test_f7_task_system_forward.py:15
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 `pipeline_v2` in sage-python/tests/test_invariant_i11.py:29
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 `pipeline_v2` in sage-python/tests/test_learning_side_effect_ledger_contract.py:13
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 `pipeline_v2` in sage-python/tests/test_model_assigner_top3_logging.py:9
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 `pipeline_v2` in sage-python/tests/test_mypy_count.py:111
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 `pipeline_v2` in sage-python/tests/test_narrative_guard.py:79
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 `pipeline_v2` in sage-python/tests/test_online_evolution.py:16
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 `pipeline_v2` in sage-python/tests/test_oracle_stack.py:230
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 `pipeline_v2` in sage-python/tests/test_oxiz_pipeline.py:8
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 `pipeline_v2` in sage-python/tests/test_phase22_deletion_contracts.py:39
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 `pipeline_v2` in sage-python/tests/test_pillar_logging.py:40
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 `pipeline_v2` in sage-python/tests/test_pipeline.py:25
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 `pipeline_v2` in sage-python/tests/test_pipeline_adaptation.py:6
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 `pipeline_v2` in sage-python/tests/test_pipeline_bandit_causality.py:15
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 `pipeline_v2` in sage-python/tests/test_pipeline_budget.py:12
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 `pipeline_v2` in sage-python/tests/test_pipeline_bypass.py:19
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 `pipeline_v2` in sage-python/tests/test_pipeline_bypass_structural_isolation.py:43
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 `pipeline_v2` in sage-python/tests/test_pipeline_fallback_provider.py:13
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 `pipeline_v2` in sage-python/tests/test_pipeline_governance.py:22
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 `pipeline_v2` in sage-python/tests/test_pipeline_periodic_save_epoch_preflight.py:60
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 `pipeline_v2` in sage-python/tests/test_pipeline_topology_flags.py:11
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 `pipeline_v2` in sage-python/tests/test_pipeline_topology_skip_guardrails_decoupling.py:74
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_bandit_attribution_invariant.py:35
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_control_surface_fields.py:85
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_fix_c_budget_tier_no_controller.py:8
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_oracle_gate_invariant.py:38
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_phase_a_wrappers.py:1
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 `pipeline_v2` in sage-python/tests/test_pipeline_v2_run_byte_identical.py:5
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 `pipeline_v2` in sage-python/tests/test_provider_execution_witness.py:29
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 `pipeline_v2` in sage-python/tests/test_provider_policy.py:13
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 `pipeline_v2` in sage-python/tests/test_provider_pool.py:477
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 `pipeline_v2` in sage-python/tests/test_reroute_runtime_integration.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 `pipeline_v2` in sage-python/tests/test_run_frame.py:199
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 `pipeline_v2` in sage-python/tests/test_system_hint.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 `pipeline_v2` in sage-python/tests/test_tool_policy.py:455
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 `pipeline_v2` in scripts/narrative_guard_phase22.py:38
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 `pipeline_v2` in scripts/phase22_inventory.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 `pytest_summary_v1` in sage-python/src/sage/runtime/evidence/producers/parsers.py:136
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 `pytest_summary_v1` in sage-python/src/sage/runtime/oracle/_oracles.py:11
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 `pytest_summary_v1` in sage-python/tests/test_runtime_evidence.py:297
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 `quality_estimator_v2` in sage-python/src/sage/quality_estimator.py:10
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 `quality_estimator_v2` in sage-python/tests/test_quality_estimator_v2.py:37
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 `swebench_pro_canary_prediction_v1` in sage-python/scripts/run_dryrun_arm_d.py:631
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 `swebench_pro_grader_preflight_v1` in sage-python/scripts/swebench_pro_grader_preflight.py:401
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 `swebench_pro_grader_preflight_v1` in sage-python/tests/test_run_dryrun_arm_d.py:2769
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_canonical_env_var_wins_over_legacy` in sage-python/tests/test_context7_tools.py:65
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_codex_extract_text_from_jsonl_v1_and_v2` in sage-python/tests/test_llm_providers.py:116
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_FW4_shutil_copy` in sage-python/tests/test_wasm_sandbox_redteam.py:279
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_normalize_chat_tools_filter_is_per_call_copy` in sage-python/tests/test_input_adapter.py:207
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_quality_estimator_v2` in sage-python/src/sage/constants.py:52
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_quality_estimator_v2` in sage-python/tests/test_e2e_integration.py:805
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_validator_strict_current_rejects_v1` in sage-python/tests/test_runtime_event_contracts.py:657
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: add_exemplar
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-discover/src/discover/adaptive_curator.py:45
low System graph software Dead code conf 1.00 Possibly dead Python function: batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/text_classification/llm.py:407
low System graph software Dead code conf 1.00 Possibly dead Python function: clear_results
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/agent_pool.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: describe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/ygn_sage/sage_candidate.py:65
low System graph software Dead code conf 1.00 Possibly dead Python function: inject_memory_context
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/agent_loop_memory.py:110
low System graph software Dead code conf 1.00 Possibly dead Python function: load_candidate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/ygn_sage/sage_candidate.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: make_local_llm
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/text_classification/llm.py:426
low System graph software Dead code conf 1.00 Possibly dead Python function: make_stub_llm
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/text_classification/llm.py:447
low System graph software Dead code conf 1.00 Possibly dead Python function: neighbors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-discover/src/discover/citation_graph.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: real_ebpf_mutate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-discover/agency_bench.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: record_decompose
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/monitoring/trace.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: record_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/monitoring/trace.py:123
low System graph software Dead code conf 1.00 Possibly dead Python function: record_reassignment
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/monitoring/trace.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: record_routing
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/monitoring/trace.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: record_topology
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-python/src/sage/monitoring/trace.py:114
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_usage
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
external/meta-harness/reference_examples/text_classification/llm.py:399
low System graph software Dead code conf 1.00 Possibly dead Python function: tool_explore_frontier
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-discover/src/discover/mcp.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: update_claim_payload
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sage-discover/src/discover/store.py:172
low System graph software Dead code conf 1.00 Possibly dead Python function: update_rules_architecture
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/sync_doc_counters.py:219
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ui/app.py:137
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Assign
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/phase22_inventory.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Attribute
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/phase22_inventory.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/phase22_inventory.py:154
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 api Wiring conf 1.00 Unused endpoint: GET /
`ui/app.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/evolution
`ui/app.py` declares `GET /api/evolution` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/memory/stats
`ui/app.py` declares `GET /api/memory/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/providers
`ui/app.py` declares `GET /api/providers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/routing/pipeline
`ui/app.py` declares `GET /api/routing/pipeline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/state
`ui/app.py` declares `GET /api/state` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/tasks
`ui/app.py` declares `GET /api/tasks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/topology
`ui/app.py` declares `GET /api/topology` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/benchmark
`ui/app.py` declares `POST /api/benchmark` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: sage-core/src/routing/bandit.rs (1913 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-core/src/routing/model_assigner.rs (3064 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-core/src/routing/system_router.rs (1769 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-core/src/topology/engine.rs (1718 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-core/src/verification/smt.rs (1442 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/scripts/generate_dataset_10k.py (1353 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/scripts/run_dryrun_arm_d.py (3530 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/src/sage/bench/swebench_bench.py (2010 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/src/sage/cli/run.py (1302 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/src/sage/runtime/event_log/payload_schemas.py (1619 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/src/sage/topology/runner.py (2597 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/tests/test_invariant_i11.py (1470 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/tests/test_pipeline.py (1492 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/tests/test_run_dryrun_arm_d.py (3681 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sage-python/tests/test_sage_cli_jsonl.py (2113 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/2dfff0fd-3692-40a2-ae24-673ff6cd81b7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2dfff0fd-3692-40a2-ae24-673ff6cd81b7/

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.