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

tgmorton/multi-model-foundry-subject-rearing

https://github.com/tgmorton/multi-model-foundry-subject-rearing · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

188 raw signals (1 security + 187 graph)

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

Complete repo analysis

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

JSON
Combined
49.3
/100
Security checks
49
1 findings
System graph
49
100.0% cov · 169 findings
Critical
1
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 1 High 2 Medium 30 Low 103 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 1 System graph 169 Crowd 0 Layer: Quality 80 Software 29 Frontend 3 Network 6 Hardware 3 Security 14 Cicd 2 Api 33
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.3/100 with 100.0% coverage. It contains 4528 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 187 findings — concentrated in quality (96), api (33), software (29). Risk profile is high: 2 critical, 2 high, 29 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 135 of 170 actionable findings. 188 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 2 occurrences Possible secret in evaluation/stimuli/transform_stimuli.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
lines 9
evaluation/stimuli/transform_stimuli.py:9 (2 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:204 SecretsClaude instruction
high System graph security auth conf 1.00 FastAPI PUT `save_note` without auth dependency — review/server.py:105
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
review/server.py:105 securityAuth fastapi unauth mutation
medium Security checks quality maintenance conf 0.70 Foundry mined blueprint gap alignment: tgmorton/multi-model-foundry-subject-rearing
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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: annotation/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 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/deploy-docs.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in annotation/static/adjudication.html:288
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
annotation/static/adjudication.html:288 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in annotation/static/admin.html:239
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
annotation/static/admin.html:239 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in annotation/static/index.html:493
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
annotation/static/index.html:493 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/validation/ablation_review.html:202
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/validation/ablation_review.html:202 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/validation/case_impoverishment_review.html:150
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/validation/case_impoverishment_review.html:150 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in review/static/index.html:620
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
review/static/index.html:620 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in review/static/reviewed.html:134
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
review/static/reviewed.html:134 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in review/sweep_dashboard.html:1715
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
review/sweep_dashboard.html:1715 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in annotation/static/adjudication.html:265
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
annotation/static/adjudication.html:265 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in annotation/static/admin.html:207
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
annotation/static/admin.html:207 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in annotation/static/index.html:443
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
annotation/static/index.html:443 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — model_foundry/trainer.py:449
`subprocess.check_output(...)` 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/_deprecated/run_experiment.py:68
`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/eval_v2_pack.py:102
`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 — scripts/fleet_status.py:96
`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/launch_cell_evals.py:73
`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/launch_production_training.py:48
`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/watch_production_training.py:36
`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 17 placeholder/mock markers across 9 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/_deprecated/p6000/run_phase_slurm.sh Ports
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
configs/sweeps/baselines/lstm_es_10m.yaml Ports
medium System graph network Security conf 1.00 Privileged port 24 in use
Port 24 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/ssrde/train.sh Ports
medium System graph network Security conf 1.00 Privileged port 48 in use
Port 48 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/ssrde/train.sh Ports
medium System graph network Security conf 1.00 Privileged port 87 in use
Port 87 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
configs/sweeps/baselines/lstm_es_10m.yaml Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1263 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: nvidia/cuda:12.1.1-cudnn8-devel-ubuntu22.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:23 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
annotation/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 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.
.github/workflows/deploy-docs.yml:25 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: evaluation/evaluators/blimp_evaluator.py:evaluate_all, evaluation/runners/threaded_blimp_evaluator.py:evaluate_all This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…
16 occurrences
repo-level (16 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: scripts/eval_v2_cell.py:model_factory, scripts/eval_v2_cell.py:model_factory, scripts/eval_v2_cell.py:model_factory This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docu…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: preprocessing/remove_expletives.py:get_spacy_device, preprocessing/remove_subject_pronominals.py:get_spacy_device, preprocessing/remove_articles.py:get_spacy_device, preprocessing/impoverish_determiners.py:get_spacy_device This is *the* AI-coder fail…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ablated_legacy` in preprocessing/tests/test_compose_corpus.py:98
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 `disfluent_copy` in analysis/corpus_descriptives/annotators/argument_structure.py:141
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 `disfluent_copy` in analysis/corpus_descriptives/annotators/clause_structure.py:209
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 `disfluent_copy` in analysis/corpus_descriptives/tests/test_annotators.py:122
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 `eval_v2` in analysis/eval_v2/compute_slor.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 `eval_v2` in analysis/eval_v2/scil_style_figures.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 `eval_v2` in evaluation/cache.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 `eval_v2` in scripts/check_cell_eval_outputs.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 `eval_v2` in scripts/eval_v2_bench.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 `eval_v2` in scripts/eval_v2_pack.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 `eval_v2` in scripts/eval_v2_smoke.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 `eval_v2` in scripts/launch_cell_evals.py:7
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 `eval_v2` in scripts/sync_eval_results_s3.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 `list_objects_v2` in model_foundry/registry.py:593
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 `list_objects_v2` in scripts/fleet_status.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 `list_objects_v2` in scripts/plot_baseline_overt_preference.py:101
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 `null_subj_v2` in scripts/eval_status.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 `null_subj_v2` in scripts/eval_v2_cell.py:53
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 `null_subj_v2` in scripts/pull_eval_results.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 `num_to_copy` in model_foundry/architectures/mamba.py:423
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 `num_to_copy` in model_foundry/architectures/rnn.py:305
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 `num_to_copy` in model_foundry/architectures/utils.py:124
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 `output_v2` in evaluation/tests/test_golden.py:30
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 `output_v2` in evaluation/tests/test_parquet_output.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 `output_v2` in evaluation/tests/test_smoke_e2e.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 `past_copy` in evaluation/core/batched_surprisal.py:260
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_get_file_tier_counts_returns_copy` in preprocessing/tests/test_remove_expletive_sentences.py:590
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: batch_calculate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/core/surprisal_calculator.py:188
low System graph software Dead code conf 1.00 Possibly dead Python function: calculate_perplexity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/core/surprisal_calculator.py:266
low System graph software Dead code conf 1.00 Possibly dead Python function: compare_experiments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/core/result_aggregator.py:171
low System graph software Dead code conf 1.00 Possibly dead Python function: estimate_dataset_size
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_checkpoint_schedule.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: evaluate_by_domain
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/evaluators/perplexity_evaluator.py:239
low System graph software Dead code conf 1.00 Possibly dead Python function: export_for_r
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/core/result_aggregator.py:258
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_utterances_from_chat
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_spanish_corpus.py:127
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_spanish_corpus.py:518
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_endtag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_spanish_corpus.py:515
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_starttag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_spanish_corpus.py:512
low System graph software Dead code conf 1.00 Possibly dead Python function: identity_doc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/identity.py:45
low System graph software Dead code conf 1.00 Possibly dead Python function: impoverish_case_en_doc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/impoverish_case.py:281
low System graph software Dead code conf 1.00 Possibly dead Python function: impoverish_case_it_doc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/impoverish_case.py:309
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_text_column
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/stimuli/normalize_simple.py:4
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_text_column
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/stimuli/normalize_text.py:4
low System graph software Dead code conf 1.00 Possibly dead Python function: pll_surprisal
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evaluation/core/pll_surprisal.py:69
low System graph software Dead code conf 1.00 Possibly dead Python function: query
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/fleet_status.py:180
low System graph software Dead code conf 1.00 Possibly dead Python function: run_data_chunking
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_deprecated/run_experiment.py:132
low System graph software Dead code conf 1.00 Possibly dead Python function: run_data_preprocessing
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_deprecated/run_experiment.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: run_dataset_tokenization
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_deprecated/run_experiment.py:116
low System graph software Dead code conf 1.00 Possibly dead Python function: run_model_training
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_deprecated/run_experiment.py:164
low System graph software Dead code conf 1.00 Possibly dead Python function: run_tokenizer_training
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_deprecated/run_experiment.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: safe_collect
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
review/serialization.py:42
low System graph software Dead code conf 1.00 Possibly dead Python function: sample_lines_line_removal
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_ablation.py:116
low System graph software Dead code conf 1.00 Possibly dead Python function: sample_lines_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_ablation.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: scrape
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/fleet_status.py:280
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_enrichment
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/enrich_verbal_morphology.py:396
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_identity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/identity.py:67
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_impoverish_case_en
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
preprocessing/ablations/impoverish_case.py:286
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/build_en_coding_guide.js:532
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/build_es_coding_guide.js:462
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`review/server.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 /adjudication
`annotation/server.py` declares `GET /adjudication` 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 /admin
`annotation/server.py` declares `GET /admin` 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/adjudication/progress
`annotation/server.py` declares `GET /api/adjudication/progress` 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/adjudication/queue
`annotation/server.py` declares `GET /api/adjudication/queue` 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/adjudication/{stimulus_id}
`annotation/server.py` declares `GET /api/adjudication/{stimulus_id}` 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/admin/users
`annotation/server.py` declares `GET /api/admin/users` 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/agreement/compute
`annotation/server.py` declares `GET /api/agreement/compute` 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/agreement/export
`annotation/server.py` declares `GET /api/agreement/export` 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/agreement/status
`annotation/server.py` declares `GET /api/agreement/status` 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/annotations/next-unannotated
`annotation/server.py` declares `GET /api/annotations/next-unannotated` 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/annotations/progress
`annotation/server.py` declares `GET /api/annotations/progress` 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/auth/me
`annotation/server.py` declares `GET /api/auth/me` 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/export/gold
`annotation/server.py` declares `GET /api/export/gold` 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/export/raw
`annotation/server.py` declares `GET /api/export/raw` 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/metadata
`review/server.py` declares `GET /api/metadata` 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/notes
`review/server.py` declares `GET /api/notes` 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/notes/enriched
`review/server.py` declares `GET /api/notes/enriched` 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/notes/export
`review/server.py` declares `GET /api/notes/export` 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/pronouns
`annotation/server.py` declares `GET /api/pronouns` 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/schematics
`review/server.py` declares `GET /api/schematics` 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/schematics/{feature}
`review/server.py` declares `GET /api/schematics/{feature}` 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/sentences
`review/server.py` declares `GET /api/sentences` 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/sentences/{sentence_id}
`review/server.py` declares `GET /api/sentences/{sentence_id}` 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/stimuli
`annotation/server.py` declares `GET /api/stimuli` 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/stimuli/starred
`annotation/server.py` declares `GET /api/stimuli/starred` 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/stimuli/{stimulus_id}
`annotation/server.py` declares `GET /api/stimuli/{stimulus_id}` 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 /reviewed
`review/server.py` declares `GET /reviewed` 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/auth/login
`annotation/server.py` declares `POST /api/auth/login` 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/stimuli/load
`annotation/server.py` declares `POST /api/stimuli/load` 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: PUT /api/adjudication/{stimulus_id}
`annotation/server.py` declares `PUT /api/adjudication/{stimulus_id}` 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: PUT /api/annotations/{stimulus_id}
`annotation/server.py` declares `PUT /api/annotations/{stimulus_id}` 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: PUT /api/notes/{sentence_id}
`review/server.py` declares `PUT /api/notes/{sentence_id}` 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: analysis/corpus_descriptives/corpus_analysis.py (2257 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analysis/corpus_descriptives/tests/test_annotators.py (1673 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analysis/scripts/reporting/generate_interactive_report.py (1883 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/90a9862e-64f4-416b-985c-689d6df4039d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/90a9862e-64f4-416b-985c-689d6df4039d/

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.