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

SciBack/guia

https://github.com/SciBack/guia · scanned 2026-06-16 00:04 UTC (2 months, 3 weeks ago)

63 raw signals (0 security + 63 graph)

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

Complete repo analysis

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

JSON
Combined
60.2
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 59 findings
Critical
0
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 0 High 2 Medium 5 Low 42 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 59 Crowd 0 Layer: Software 17 Hardware 2 Frontend 1 Security 4 Cicd 1 Quality 22 Api 12
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 60.2/100 with 100.0% coverage. It contains 1227 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 63 findings — concentrated in quality (25), software (17), api (12). Risk profile is high: 0 critical, 2 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 49 of 59 actionable findings. 63 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.

high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — src/guia/api/routes/chat.py:17
`@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/guia/api/routes/chat.py:17 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `embeddings` without auth dependency — src/guia/embeddings_sidecar.py:113
`@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/guia/embeddings_sidecar.py:113 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/auto-login.js:356
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing operator-readme. 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/auto-login.js:40
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/auto-login.js:40 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/auto-login.js:134
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/auto-login.js:134 Insert adjacent html
low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AZURE_TENANT_ID`, `CHAINLIT_URL`, `GUIA_ADMIN_TOKEN`, `GUIA_S3_FEEDBACK_BUCKET`, `NVIDIA_NIM_API_KEY`, `OAUTH_KEYCLOAK_BASE_URL`, `OAUTH_KEYCLOAK_CLIENT_ID`, `OAUTH_KEYCLOAK_CLIENT_SECRET` + 1 more. Add them (with a placeholder/comment) to .env.ex…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 21 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.13-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 32
docker/api/Dockerfile:2, 32 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:31 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/guia/routing/gates.py:evaluate, src/guia/routing/gates.py:evaluate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
3 occurrences
repo-level (3 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: src/guia/audit/repository.py:close, src/guia/services/history.py:close, src/guia/services/telegram_link.py:close This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or documen…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `agent_orchestrator_timeout_fallback_legacy` in src/guia/services/chat.py:636
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/guia/services/search.py:76
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_chat_agent_timeout_falls_back_to_legacy` in tests/unit/test_chat_service.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 `test_none_user_id_is_legacy` in tests/services/test_bucket.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 software Dead code conf 1.00 Possibly dead Python function: backup_s3_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/scheduler/jobs.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: correct_typos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/nlp/speller.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/services/history.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: expand_on_zero_hits
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/services/query_rewriter.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_entities
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/nlp/ner.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: feedback_export_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/scheduler/jobs.py:230
low System graph software Dead code conf 1.00 Possibly dead Python function: harvest_daily_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/scheduler/jobs.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: harvest_koha_weekly_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/scheduler/jobs.py:104
low System graph software Dead code conf 1.00 Possibly dead Python function: hybrid_async
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/search/backend.py:114
low System graph software Dead code conf 1.00 Possibly dead Python function: hybrid_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/search/backend.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: index_async
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/search/backend.py:110
low System graph software Dead code conf 1.00 Possibly dead Python function: metrics_report_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/scheduler/jobs.py:313
low System graph software Dead code conf 1.00 Possibly dead Python function: pdf_to_chunks
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/pdf/grobid.py:138
low System graph software Dead code conf 1.00 Possibly dead Python function: process_header_only
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/pdf/grobid.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: save_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/services/history.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: update_opt_ins
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/services/profile.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_token_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/guia/auth/identity.py:224
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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: DELETE /
`src/guia/api/routes/profile.py` declares `DELETE /` 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: DELETE /link
`src/guia/api/routes/telegram_link.py` declares `DELETE /link` 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/guia/api/routes/oai.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 /audit
`src/guia/api/routes/admin.py` declares `GET /audit` 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 /export
`src/guia/api/routes/profile.py` declares `GET /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 /feedback/export
`src/guia/api/routes/admin.py` declares `GET /feedback/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 /feedback/stats
`src/guia/api/routes/admin.py` declares `GET /feedback/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/embeddings
`src/guia/embeddings_sidecar.py` declares `POST /api/embeddings` 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 /chat
`src/guia/api/routes/chat.py` declares `POST /chat` 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 /harvest
`src/guia/api/routes/harvest.py` declares `POST /harvest` 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 /link
`src/guia/api/routes/telegram_link.py` declares `POST /link` 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 /opt-ins
`src/guia/api/routes/profile.py` declares `POST /opt-ins` 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
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/0ad544bb-3489-4718-850b-e3677b02cc6d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0ad544bb-3489-4718-850b-e3677b02cc6d/

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.