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

zhaksylykanuar/company-knowledge-os

https://github.com/zhaksylykanuar/company-knowledge-os · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

134 raw signals (32 security + 102 graph)

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

Complete repo analysis

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

JSON
Combined
59.5
/100
Security checks
60
8 findings
System graph
60
100.0% cov · 85 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 17 Medium 8 Low 64 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 85 Crowd 0 Layer: Quality 37 Software 10 Hardware 1 Frontend 1 Security 14 Cicd 1 Api 29
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 59.5/100 with 100.0% coverage. It contains 4371 nodes across 29 cross-layer flows, written primarily in mixed languages. Engine surfaced 102 findings — concentrated in quality (46), api (29), security (14). Risk profile is high: 1 critical, 13 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 91 of 93 actionable findings. 211 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 Security checks quality Practices conf 0.82 Foundry mined mock as real or placeholder: zhaksylykanuar/company-knowledge-os
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
critical System graph security Secrets conf 1.00 Possible secret in app/services/atlassian_api_profiles.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
app/services/atlassian_api_profiles.py:25
high Security checks quality Practices conf 0.84 25 occurrences Foundry mined bad chains: zhaksylykanuar/company-knowledge-os
Comment chain pattern product: bad_chains Repo: zhaksylykanuar/company-knowledge-os Thread: zhaksylykanuar/company-knowledge-os#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph…
25 occurrences
repo-level (25 hits)
high Security checks quality Practices conf 0.80 6 occurrences Foundry mined docs only runtime fix: zhaksylykanuar/company-knowledge-os
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: assumption_chec…
6 occurrences
repo-level (6 hits)
high Security checks quality Quality conf 0.76 Foundry mined schema ui api mismatch: zhaksylykanuar/company-knowledge-os
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: assumption_check Repo: zhaksylykanuar…
high Security checks quality Testing conf 0.78 25 occurrences Foundry mined test ci gap after feedback: zhaksylykanuar/company-knowledge-os
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: assumption_check Repo: …
25 occurrences
repo-level (25 hits)
high System graph security auth conf 1.00 FastAPI POST `approve_persisted_digest_delivery_draft_endpoint` without auth dependency — app/api/digest.py:651
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/digest.py:651 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ask_knowledge_endpoint` without auth dependency — app/api/knowledge.py:90
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/knowledge.py:90 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_persisted_attention_digest_delivery_draft_endpoint` without auth dependency — app/api/digest.py:623
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/digest.py:623 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_persisted_digest_delivery_intention_endpoint` without auth dependency — app/api/digest.py:693
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/digest.py:693 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `drive_backfill` without auth dependency — app/api/drive.py:195
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/drive.py:195 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `extract_demo` without auth dependency — app/api/extraction.py:19
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/extraction.py:19 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gmail_backfill` without auth dependency — app/api/gmail.py:447
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/gmail.py:447 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_event` without auth dependency — app/api/events.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/events.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_text_endpoint` without auth dependency — app/api/knowledge.py:35
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/knowledge.py:35 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_text_process_endpoint` without auth dependency — app/api/knowledge.py:61
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/knowledge.py:61 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `process_document` without auth dependency — app/api/extraction.py:33
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/extraction.py:33 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reject_persisted_digest_delivery_draft_endpoint` without auth dependency — app/api/digest.py:663
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/digest.py:663 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `score_knowledge_endpoint` without auth dependency — app/api/knowledge.py:94
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/knowledge.py:94 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 Foundry mined assumption checks: zhaksylykanuar/company-knowledge-os
Comment chain pattern product: assumption_checks Repo: zhaksylykanuar/company-knowledge-os Thread: zhaksylykanuar/company-knowledge-os#24 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_…
medium Security checks quality maintenance conf 0.70 25 occurrences Foundry mined blueprint gap alignment: zhaksylykanuar/company-knowledge-os
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: …
25 occurrences
repo-level (25 hits)
medium Security checks quality Practices conf 0.70 25 occurrences Foundry mined unresolved feedback: zhaksylykanuar/company-knowledge-os
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: assu…
25 occurrences
repo-level (25 hits)
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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:39 CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/report_ignored_file_cleanup_plan.py:139
`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 12 placeholder/mock markers across 6 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Maintenance conf 1.00 36 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
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 187 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 quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 14 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/plan_jira_write_readiness.py:run_jira_write_readiness, scripts/doctor_external_connector_config.py:run_external_connector_config_doctor This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-h…
14 occurrences
repo-level (14 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/check_github_org_readonly_inventory.py:run_github_org_readonly_inventory, scripts/check_jira_readonly_inventory.py:run_jira_readonly_inventory, app/services/github_org_inventory.py:run_github_org_readonly_inventory This is *the* AI-coder fail…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/preview_founder_digest.py:main, scripts/run_telegram_founder_bot.py:main, scripts/list_github_repos_readonly.py:main, scripts/list_jira_projects_readonly.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…
3 occurrences
repo-level (3 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 `_gmail_old` in tests/test_email_attention.py:556
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 `attention_triage_llm_vs_deterministic_v1` in scripts/compare_attention_triage_llm_vs_deterministic.py:49
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deterministic_v1` in app/services/email_threads.py:1073
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 `founder_v2` in scripts/prepare_no_marker_persisted_attention_delivery_draft.py:46
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 app/services/attention_results.py:160
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 app/services/attention_triage.py:279
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in app/services/email_attention.py:348
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `review_json_legacy` in scripts/report_no_marker_persisted_attention_grouped_lifecycle_compatibility.py:1420
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 `review_json_legacy` in tests/test_no_marker_grouped_lifecycle_compatibility.py:1754
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: create_project_status_snapshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/status_engine.py:141
low System graph software Dead code conf 1.00 Possibly dead Python function: forbidden_transport
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/check_external_connectors_readonly.py:532
low System graph software Dead code conf 1.00 Possibly dead Python function: forbidden_transport
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/doctor_guarded_execution.py:282
low System graph software Dead code conf 1.00 Possibly dead Python function: guarded_transport
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/check_github_org_readonly_inventory.py:138
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.
app/api/gmail.py:108
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.
app/api/gmail.py:104
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.
app/api/gmail.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: read_gmail_counts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_fos_036_gmail.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: require_api_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/api/auth.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: require_api_key_for_config
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/api/auth.py:60
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`app/api/health.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 /attention
`app/api/knowledge.py` declares `GET /attention` 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 /backfill/preflight
`app/api/google.py` declares `GET /backfill/preflight` 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 /delivery-drafts/{delivery_draft_id}
`app/api/digest.py` declares `GET /delivery-drafts/{delivery_draft_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 /delivery-drafts/{delivery_draft_id}/approval-status
`app/api/digest.py` declares `GET /delivery-drafts/{delivery_draft_id}/approval-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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /delivery-drafts/{delivery_draft_id}/delivery-readiness
`app/api/digest.py` declares `GET /delivery-drafts/{delivery_draft_id}/delivery-readiness` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /delivery-intentions/{delivery_intention_id}
`app/api/digest.py` declares `GET /delivery-intentions/{delivery_intention_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 /delivery-intentions/{delivery_intention_id}/telegram-execution-gate
`app/api/digest.py` declares `GET /delivery-intentions/{delivery_intention_id}/telegram-execution-gate` 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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /delivery-intentions/{delivery_intention_id}/telegram-execution-preflight
`app/api/digest.py` declares `GET /delivery-intentions/{delivery_intention_id}/telegram-execution-preflight` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /delivery-intentions/{delivery_intention_id}/telegram-plan
`app/api/digest.py` declares `GET /delivery-intentions/{delivery_intention_id}/telegram-plan` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /delivery-results/{delivery_result_id}
`app/api/digest.py` declares `GET /delivery-results/{delivery_result_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 /persisted-attention
`app/api/digest.py` declares `GET /persisted-attention` 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 /persisted-attention/delivery-draft
`app/api/digest.py` declares `GET /persisted-attention/delivery-draft` 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 /persisted-attention/text
`app/api/digest.py` declares `GET /persisted-attention/text` 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 /search
`app/api/knowledge.py` declares `GET /search` 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 /source-activity
`app/api/digest.py` declares `GET /source-activity` 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 /source-activity/text
`app/api/digest.py` declares `GET /source-activity/text` 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 /
`app/api/events.py` declares `POST /` 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 /ask
`app/api/knowledge.py` declares `POST /ask` 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 /backfill
`app/api/gmail.py` declares `POST /backfill` 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 /delivery-drafts/{delivery_draft_id}/approve
`app/api/digest.py` declares `POST /delivery-drafts/{delivery_draft_id}/approve` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /delivery-drafts/{delivery_draft_id}/delivery-intention
`app/api/digest.py` declares `POST /delivery-drafts/{delivery_draft_id}/delivery-intention` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /delivery-drafts/{delivery_draft_id}/reject
`app/api/digest.py` declares `POST /delivery-drafts/{delivery_draft_id}/reject` 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 /demo
`app/api/extraction.py` declares `POST /demo` 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 /ingest-text
`app/api/knowledge.py` declares `POST /ingest-text` 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 /ingest-text-process
`app/api/knowledge.py` declares `POST /ingest-text-process` 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 /persisted-attention/delivery-draft
`app/api/digest.py` declares `POST /persisted-attention/delivery-draft` 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 /process-document
`app/api/extraction.py` declares `POST /process-document` 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 /score
`app/api/knowledge.py` declares `POST /score` 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: app/services/digest_delivery_drafts.py (2846 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/report_no_marker_persisted_attention_grouped_lifecycle_compatibility.py (1856 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_digest_api.py (3252 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_digest_delivery_drafts.py (3831 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_digest_service.py (1394 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_manual_no_marker_grouped_lifecycle_review.py (1675 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_no_marker_grouped_lifecycle_compatibility.py (1950 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/06a38800-c490-43ba-95af-8a4c0b8c5ea7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/06a38800-c490-43ba-95af-8a4c0b8c5ea7/

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.