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

WhalerMike/uiao

https://github.com/WhalerMike/uiao · scanned 2026-06-16 01:01 UTC (2 months, 1 week ago)

365 raw signals (0 security + 365 graph)

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

Complete repo analysis

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

JSON
Combined
51.0
/100
Security checks
51
0 findings
System graph
51
100.0% cov · 171 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 4 Medium 18 Low 111 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 171 Crowd 0 Layer: Software 25 Frontend 4 Network 2 Hardware 2 Security 8 Cicd 3 Quality 88 Api 39
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 51.0/100 with 100.0% coverage. It contains 11209 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 365 findings — concentrated in cicd (180), quality (104), api (39). Risk profile is high: 1 critical, 4 high, 54 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in .github/workflows/azure-saas-deploy.yml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
.github/workflows/azure-saas-deploy.yml:92
high System graph api Wiring conf 1.00 Dangling fetch: POST /orgpath/api/govern (src/uiao/api/web/static/app.js:60)
`src/uiao/api/web/static/app.js:60` calls `POST /orgpath/api/govern` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/orgpath/api/govern` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `run_governance` without auth dependency — src/uiao/api/web/console.py:276
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/uiao/api/web/console.py:276 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate` without auth dependency — src/uiao/api/routes/orgpath.py:223
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/uiao/api/routes/orgpath.py:223 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in scripts/enforcement_orchestrator.py:34
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
scripts/enforcement_orchestrator.py:34 Tls verify false
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.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.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 cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned
azure/login@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
11 files, 13 locations
.github/workflows/release.yml:66, 99 (2 hits)
docs/.github/workflows/link-check.yml:65, 114 (2 hits)
.github/workflows/azure-saas-deploy.yml:52
.github/workflows/link-check.yml:37
.github/workflows/pwsh-pack.yml:89
.github/workflows/release-drafter.yml:19
docs/.github/workflows/build-docs.yml:47
docs/.github/workflows/canon-sync-receive.yml:138
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 25 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
12 files, 12 locations
.github/workflows/azure-saas-deploy.yml
.github/workflows/diagrams-ci.yaml
.github/workflows/image-gen.yml
.github/workflows/orchestrator-schedule-nightly.yml
.github/workflows/pwsh-pack.yml
.github/workflows/quarto.yml
.github/workflows/release-drafter.yml
.github/workflows/release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/uiao/api/web/static/app.js:32
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/uiao/api/web/static/app.js:32 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in docs/scripts/metadata_drift_scan.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
docs/scripts/metadata_drift_scan.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in docs/scripts/update_corpus_index.js:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
docs/scripts/update_corpus_index.js:9 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — diagrams/scripts/pre-render.py:50
`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/cyberark_sync_orchestrator.py:72
`requests.post(...)` 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/enforcement_orchestrator.py:62
`requests.post(...)` 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/reorganize_monorepo.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/sync_orchestrator.py:132
`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 — scripts/validate_fedramp.py:29
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/uiao/cli/init.py:171
`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 98 placeholder/mock markers across 40 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 498 in use
Port 498 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
src/uiao/canon/release-manifests/platform-server-v1.2.yaml Ports
medium System graph network Security conf 1.00 Privileged port 914 in use
Port 914 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
src/uiao/canon/release-manifests/platform-server-v1.2.yaml Ports
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 958 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 10, 36
deploy/azure/Dockerfile:10, 36 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 142 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
12 files, 56 locations
.github/workflows/quarto.yml:43, 76, 92, 140, 158, 164, 192, 199, +3 more (11 hits)
.github/workflows/conmon-aggregate.yml:46, 49, 91, 104, 153 (5 hits)
.github/workflows/release.yml:27, 32, 75, 90, 93 (5 hits)
docs/.github/workflows/drift-scan.yml:24, 30, 37, 96, 104 (5 hits)
.github/workflows/image-gen.yml:95, 130, 138, 178 (4 hits)
.github/workflows/pytest.yml:23, 26, 43, 46 (4 hits)
docs/.github/workflows/canon-sync-receive.yml:45, 48, 56, 83 (4 hits)
docs/.github/workflows/dashboard-export.yml:19, 25, 32, 90 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: diagrams/scripts/validate.py:parse_frontmatter, diagrams/scripts/render.py:parse_frontmatter This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separa…
15 occurrences
repo-level (15 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/add_qmd_format_block.py:main, scripts/regenerate_local_images_from_figalt.py:main, scripts/add_lifecycle_to_qmd.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consoli…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/generate_substrate_status_table.py:main, scripts/generate_sitemap.py:main, scripts/generate_customer_docs_status.py:main, scripts/generate_document_index.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: inbox/drafts/phase2-runtime-drift-validators/validators.py:check, inbox/drafts/phase2-runtime-drift-validators/validators.py:check, inbox/drafts/phase2-runtime-drift-validators/validators.py:check, inbox/drafts/phase2-runtime-drift-validators/validato…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `canon_refs_deprecated` in scripts/generate_images.py:208
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 `CanonicalLegacy` in tests/test_drift_output.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 `cd_copy` in tests/test_servicenow_oscal_emitter.py:245
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 `has_copy` in scripts/tools/appendix_indexer.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 `is_deprecated` in src/uiao/api/routes/orgpath.py:20
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 `is_deprecated` in src/uiao/api/web/console.py:183
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 `is_deprecated` in src/uiao/governance/drift.py:333
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 `is_deprecated` in src/uiao/governance/drift_engine.py:294
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 `is_deprecated` in src/uiao/modernization/orgtree/codebook.py:24
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 `is_deprecated` in tests/test_orgpath_codebook.py:200
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 `leadership_briefing_v1` in src/uiao/generators/docs.py:80
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 `leadership_briefing_v1` in src/uiao/generators/rich_docx.py:699
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in inbox/drafts/phase0-runtime-provenance-envelope/provenance.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 `model_copy` in src/uiao/adapters/scuba/ir/transformer.py:108
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/uiao/saas/tenant.py:109
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 `nLegacy` in tests/test_substrate_walker.py:392
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 `tags_old` in docs/tools/uiao-governance-cli.js:41
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_codebook_serializes_deprecated` in tests/orgtree/test_orgpath_api.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 `UIAO_002_SCuBA_Technical_Specification_v1` in docs/docs/session-logs/scripts/fix_uiao_002.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 `UIAO_002_SCuBA_Technical_Specification_v1` in scripts/reorganize_monorepo.py:120
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 `UIAO_003_Adapter_Segmentation_Overview_v1` in docs/docs/session-logs/scripts/canon_backfill.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 `UIAO_007_OrgTree_Modernization_AD_to_EntraID_v1` in tests/test_active_directory_survey_enrichment.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 `uiao_jml_logic_v1` in tests/canon_paths.py:42
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 `uiao_leadership_briefing_v1` in src/uiao/cli/generate.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 `uiao_leadership_briefing_v1` in src/uiao/generators/pptx.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 `uiao_leadership_briefing_v1` in src/uiao/generators/ssp.py:652
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 `uiao_leadership_briefing_v1` in src/uiao/models/canon.py:67
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `uiao_leadership_briefing_v1` in src/uiao/utils/context.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 `uiao_leadership_briefing_v1` in tests/test_e2e.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 `uiao_leadership_briefing_v1` in tests/test_models.py:119
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 `uiao_pitch_deck_v1` in scripts/generate_pptx.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 `uiao_project_plan_v1` in scripts/plan_to_csv.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 `winserver_legacy` in src/uiao/adapters/modernization/active_directory/intune_readiness.py:202
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 `with_copy` in scripts/tools/dashboard_exporter.py:117
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: abbreviate_match
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
diagrams/scripts/render.py:209
low System graph software Dead code conf 1.00 Possibly dead Python function: appendix_sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/charter-preprocessor/atobz_preprocess.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: build_pipeline
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase2-runtime-drift-validators/validators.py:350
low System graph software Dead code conf 1.00 Possibly dead Python function: chapter_sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/rebuild_orgpath_image_manifest.py:240
low System graph software Dead code conf 1.00 Possibly dead Python function: check_certificate_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/uiao/adapters/pkica_adapter.py:118
low System graph software Dead code conf 1.00 Possibly dead Python function: compute_frontmatter_hash
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/tools/sync_canon.py:364
low System graph software Dead code conf 1.00 Possibly dead Python function: fix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase3-remediation-contract-and-router/remediation_router.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_endpoint_evidence
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/uiao/adapters/intune_adapter.py:157
low System graph software Dead code conf 1.00 Possibly dead Python function: hygiene_finding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase3-remediation-contract-and-router/drift_finding.py:191
low System graph software Dead code conf 1.00 Possibly dead Python function: model_post_init
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/uiao/config.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: new_claim_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase0-runtime-provenance-envelope/provenance.py:248
low System graph software Dead code conf 1.00 Possibly dead Python function: new_run_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/New_FedRAMP_Boundary/inject_images_into_docs.py:204
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_graph_entities
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/uiao/adapters/m365_parser.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_security_policies
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/uiao/adapters/m365_parser.py:64
low System graph software Dead code conf 1.00 Possibly dead Python function: register_fix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase3-remediation-contract-and-router/remediation_router.py:264
low System graph software Dead code conf 1.00 Possibly dead Python function: render_real
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
docs/tools/generate_images.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: render_stub
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
docs/tools/generate_images.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: replacer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/fix_concept_lists.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: replacer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/charter-preprocessor/atobz_preprocess.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: route_many
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase3-remediation-contract-and-router/remediation_router.py:287
low System graph software Dead code conf 1.00 Possibly dead Python function: runtime_finding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase3-remediation-contract-and-router/drift_finding.py:214
low System graph software Dead code conf 1.00 Possibly dead Python function: seal
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase0-runtime-provenance-envelope/provenance.py:185
low System graph software Dead code conf 1.00 Possibly dead Python function: sha256_prompt_file
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_images.py:242
low System graph software Dead code conf 1.00 Possibly dead Python function: to_telemetry_event
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase0-runtime-provenance-envelope/provenance.py:222
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_chain
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
inbox/drafts/phase0-runtime-provenance-envelope/provenance.py:206
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 — docs/scripts/metadata_drift_scan.js:125
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 — docs/scripts/update_corpus_index.js:96
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 — docs/tools/uiao-governance-cli.js:52
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: DELETE /tenants/{tenant_id}
`src/uiao/saas/control_plane.py` declares `DELETE /tenants/{tenant_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 /
`src/uiao/api/routes/ztmm.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/auditor/evidence
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/evidence` 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/auditor/evidence/{evidence_id}
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/evidence/{evidence_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auditor/findings
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/findings` 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/auditor/graph/{control_id}
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/graph/{control_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/auditor/oscal/poam
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/oscal/poam` 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/auditor/oscal/sap
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/oscal/sap` 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/auditor/oscal/sar
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/oscal/sar` 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/auditor/oscal/ssp
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/oscal/ssp` 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/auditor/poam
`src/uiao/api/routes/auditor.py` declares `GET /api/auditor/poam` 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/v1/archive
`src/uiao/api/routes/archive.py` declares `GET /api/v1/archive` 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/v1/archive/{run_id}/{adapter_id}
`src/uiao/api/routes/archive.py` declares `GET /api/v1/archive/{run_id}/{adapter_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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/orgpath/codebook
`src/uiao/api/routes/orgpath.py` declares `GET /api/v1/orgpath/codebook` 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/v1/orgpath/drift
`src/uiao/api/routes/orgpath.py` declares `GET /api/v1/orgpath/drift` 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/v1/orgpath/principals/{principal_id}/facets
`src/uiao/api/routes/orgpath.py` declares `GET /api/v1/orgpath/principals/{principal_id}/facets` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /codebook
`src/uiao/api/web/console.py` declares `GET /codebook` 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 /gaps
`src/uiao/api/routes/boundary.py` declares `GET /gaps` 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 /govern
`src/uiao/api/web/console.py` declares `GET /govern` 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 /journal
`src/uiao/api/routes/enforcement.py` declares `GET /journal` 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 /policies
`src/uiao/api/routes/epl.py` declares `GET /policies` 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 /policies/{policy_id}
`src/uiao/api/routes/epl.py` declares `GET /policies/{policy_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 /principals
`src/uiao/api/web/console.py` declares `GET /principals` 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 /queries
`src/uiao/api/routes/cql.py` declares `GET /queries` 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 /queries/{name}
`src/uiao/api/routes/cql.py` declares `GET /queries/{name}` 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 /tenants
`src/uiao/saas/control_plane.py` declares `GET /tenants` 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 /tenants/{tenant_id}
`src/uiao/saas/control_plane.py` declares `GET /tenants/{tenant_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 /{pillar}
`src/uiao/api/routes/ztmm.py` declares `GET /{pillar}` 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/govern
`src/uiao/api/web/console.py` declares `POST /api/govern` 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/v1/orgpath/validate
`src/uiao/api/routes/orgpath.py` declares `POST /api/v1/orgpath/validate` 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 /dispatch
`src/uiao/api/routes/enforcement.py` declares `POST /dispatch` 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 /evaluate
`src/uiao/api/routes/epl.py` declares `POST /evaluate` 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 /evaluate/{name}
`src/uiao/api/routes/cql.py` declares `POST /evaluate/{name}` 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 /findings
`src/uiao/api/routes/survey.py` declares `POST /findings` 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 /run
`src/uiao/api/routes/boundary.py` declares `POST /run` 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 /tenants
`src/uiao/saas/control_plane.py` declares `POST /tenants` 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 /tenants/{tenant_id}/resume
`src/uiao/saas/control_plane.py` declares `POST /tenants/{tenant_id}/resume` 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 /tenants/{tenant_id}/suspend
`src/uiao/saas/control_plane.py` declares `POST /tenants/{tenant_id}/suspend` 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: scripts/generate_images.py (1387 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/uiao/adapters/modernization/active_directory/survey.py (1742 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/5246650d-7040-4c22-9d08-6c80115fe275/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5246650d-7040-4c22-9d08-6c80115fe275/

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.