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

thanhuy8888/-n_Systematic-Review-AI

https://github.com/thanhuy8888/-n_Systematic-Review-AI · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

68 raw signals (0 security + 68 graph)

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

Complete repo analysis

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

JSON
Combined
69.4
/100
Security checks
69
0 findings
System graph
69
100.0% cov · 60 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 13 Medium 9 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 60 Crowd 0 Layer: Software 5 Frontend 3 Hardware 7 Security 13 Cicd 1 Quality 13 Api 18
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 69.4/100 with 100.0% coverage. It contains 321 nodes across 16 cross-layer flows, written primarily in mixed languages. Engine surfaced 68 findings — concentrated in quality (21), api (18), security (13). Risk profile is high: 0 critical, 13 high, 9 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 55 of 60 actionable findings. 68 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 api Wiring conf 1.00 Dangling fetch: GET /sample_project.json (apps/web/App.tsx:315)
`apps/web/App.tsx:315` calls `GET /sample_project.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sample_project.json` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:8000/screening/parse_pdf (apps/web/components/PaperUploader.tsx:33)
`apps/web/components/PaperUploader.tsx:33` calls `POST http://localhost:8000/screening/parse_pdf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8000/screening/parse_pdf` If this points at an externa…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_paper` without auth dependency — apps/api/routers/screening.py:266
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:266 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `submit_correction` without auth dependency — apps/api/routers/review.py:192
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/review.py:192 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `accept_extraction` without auth dependency — apps/api/routers/review.py:213
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/review.py:213 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `extract_data` without auth dependency — apps/api/routers/screening.py:173
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:173 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `parse_pdf_file` without auth dependency — apps/api/routers/screening.py:221
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:221 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `persist_extraction` without auth dependency — apps/api/routers/review.py:65
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/review.py:65 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `predict_screening` without auth dependency — apps/api/routers/screening.py:123
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:123 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reject_extraction` without auth dependency — apps/api/routers/review.py:233
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/review.py:233 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_review_action` without auth dependency — apps/api/routers/screening.py:91
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_retrain` without auth dependency — apps/api/routers/screening.py:164
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/screening.py:164 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_files` without auth dependency — apps/api/routers/upload.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.
apps/api/routers/upload.py:19 securityAuth fastapi unauth mutation
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: transformers
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:23 containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: apps/web/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/api/main.py:13
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/api/main.py:13 Cors wildcard
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 24 placeholder/mock markers across 4 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 quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 41 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
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 196 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.25-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/web/Dockerfile:14 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/web/Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.10-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:3 containersPinned dependencies
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: experiments/baselines/train_ensemble_cpu.py:load_dataset, experiments/baselines/finetune_pubmedbert_cpu.py:load_dataset This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or …
7 occurrences
repo-level (7 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: experiments/baselines/compare_models.py:load_data, experiments/baselines/evaluate_heuristic.py:load_data, experiments/baselines/evaluate_baseline.py:load_data This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://…
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 software Dead code conf 1.00 Possibly dead Python function: active_learning_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/routers/screening.py:159
low System graph software Dead code conf 1.00 Possibly dead Python function: build_index
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sr_core/screening_model/bm25.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: flatten_tables
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sr_core/ingest/parser.py:154
low System graph software Dead code conf 1.00 Possibly dead Python function: merge_rayyan_export_folders
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sr_core/ingest/rayyan_parser.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: plot_results
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sr_core/screening_model/baseline.py:110
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 — apps/web/App.tsx:225
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 — apps/web/components/PaperUploader.tsx:32
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 /{paper_id}
`apps/api/routers/screening.py` declares `DELETE /{paper_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 /
`apps/api/main.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 /extractions
`apps/api/routers/review.py` declares `GET /extractions` 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 /extractions/{extraction_id}
`apps/api/routers/review.py` declares `GET /extractions/{extraction_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 /queue
`apps/api/routers/review.py` declares `GET /queue` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stats
`apps/api/routers/review.py` declares `GET /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: PATCH /extractions/{extraction_id}
`apps/api/routers/review.py` declares `PATCH /extractions/{extraction_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: POST /
`apps/api/routers/upload.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 /extract
`apps/api/routers/screening.py` declares `POST /extract` 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 /extractions/persist
`apps/api/routers/review.py` declares `POST /extractions/persist` 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 /extractions/{extraction_id}/accept
`apps/api/routers/review.py` declares `POST /extractions/{extraction_id}/accept` 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 /extractions/{extraction_id}/reject
`apps/api/routers/review.py` declares `POST /extractions/{extraction_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /parse_pdf
`apps/api/routers/screening.py` declares `POST /parse_pdf` 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 /predict
`apps/api/routers/screening.py` declares `POST /predict` 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 /retrain
`apps/api/routers/screening.py` declares `POST /retrain` 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 /{paper_id}/action
`apps/api/routers/screening.py` declares `POST /{paper_id}/action` 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: apps/web/App.tsx (816 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/c25e07d0-b1d9-4ab8-97c2-a166d099bd87/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c25e07d0-b1d9-4ab8-97c2-a166d099bd87/

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.