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

zx2015/doc2md

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

43 raw signals (0 security + 43 graph)

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

Complete repo analysis

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

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

Showing 32 of 34 actionable findings. 43 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: DELETE /api/v1/jobs/${id} (frontend/src/features/dashboard/Dashboard.tsx:52)
`frontend/src/features/dashboard/Dashboard.tsx:52` calls `DELETE /api/v1/jobs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/jobs/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/jobs/${id} (frontend/src/features/dashboard/Dashboard.tsx:66)
`frontend/src/features/dashboard/Dashboard.tsx:66` calls `DELETE /api/v1/jobs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/jobs/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/config (frontend/src/features/settings/Settings.tsx:9)
`frontend/src/features/settings/Settings.tsx:9` calls `GET /api/v1/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/config` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/jobs/${jobId}/result (frontend/src/features/preview/Preview.tsx:13)
`frontend/src/features/preview/Preview.tsx:13` calls `GET /api/v1/jobs/${jobId}/result` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/jobs/<p>/result` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/jobs?limit=20 (frontend/src/features/dashboard/Dashboard.tsx:39)
`frontend/src/features/dashboard/Dashboard.tsx:39` calls `GET /api/v1/jobs?limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/jobs` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/config/test (frontend/src/features/settings/Settings.tsx:34)
`frontend/src/features/settings/Settings.tsx:34` calls `POST /api/v1/config/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/config/test` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/jobs (frontend/src/features/dashboard/Dashboard.tsx:118)
`frontend/src/features/dashboard/Dashboard.tsx:118` calls `POST /api/v1/jobs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/jobs` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/v1/config (frontend/src/features/settings/Settings.tsx:18)
`frontend/src/features/settings/Settings.tsx:18` calls `PUT /api/v1/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/config` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_job` without auth dependency — backend/app/api/v1/jobs.py:112
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/jobs.py:112 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_job` without auth dependency — backend/app/api/v1/jobs.py:23
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/jobs.py:23 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_connection` without auth dependency — backend/app/api/v1/config.py:54
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/config.py:54 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_config` without auth dependency — backend/app/api/v1/config.py:36
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/config.py:36 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/features/dashboard/Dashboard.tsx:118
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 license, ci, 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme. 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 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 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
low System graph quality Tests conf 1.00 Low test-to-source ratio
7 tests / 38 src (ratio 0.18).
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/api/deps.py:init_app_config, backend/app/api/v1/config.py:get_config 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.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 5 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
5 files, 5 locations
backend/alembic/versions/013f124caf70_add_vlm_model.py:27
backend/alembic/versions/08396e620f25_vlm_model.py:27
backend/alembic/versions/27dda7dc1d47_v107_fields.py:36
backend/alembic/versions/40e4e2c7bcd2_add_mineru_options.py:31
backend/alembic/versions/43e61d7dd24d_init_db.py:79
low System graph software Dead code conf 1.00 5 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
5 files, 5 locations
backend/alembic/versions/013f124caf70_add_vlm_model.py:21
backend/alembic/versions/08396e620f25_vlm_model.py:21
backend/alembic/versions/27dda7dc1d47_v107_fields.py:21
backend/alembic/versions/40e4e2c7bcd2_add_mineru_options.py:21
backend/alembic/versions/43e61d7dd24d_init_db.py:21
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 /jobs/{job_id}
`backend/app/api/v1/jobs.py` declares `DELETE /jobs/{job_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 /config
`backend/app/api/v1/config.py` declares `GET /config` 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 /jobs
`backend/app/api/v1/jobs.py` declares `GET /jobs` 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 /jobs/{job_id}/result
`backend/app/api/v1/jobs.py` declares `GET /jobs/{job_id}/result` 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 /config/test
`backend/app/api/v1/config.py` declares `POST /config/test` 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 /jobs
`backend/app/api/v1/jobs.py` declares `POST /jobs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /config
`backend/app/api/v1/config.py` declares `PUT /config` 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/40b58890-859a-4a13-821a-24ad4d250bb9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/40b58890-859a-4a13-821a-24ad4d250bb9/

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.