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.

zhouqb/auto-researcher

https://github.com/zhouqb/auto-researcher · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

38 raw signals (0 security + 38 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 36 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 8 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 36 Crowd 0 Layer: Software 2 Frontend 2 Security 1 Cicd 1 Quality 16 Api 14

Exclude dismissed / FP Exclude test files

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 77.2/100 with 100.0% coverage. It contains 538 nodes across 15 cross-layer flows, written primarily in mixed languages. Engine surfaced 38 findings — concentrated in quality (18), api (14), software (2). Risk profile is low: 0 critical, 0 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 29 of 36 actionable findings. 38 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.

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 ci. 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/live_e2e_repo.py:51

`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/deep_researcher/codex/workspace.py:184

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/deep_researcher/tools/codex.py:78

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/deep_researcher/tools/repo.py:105

runtime safetyRobustness

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 Debug conf 1.00 Debug logging residue appears in source files

Found 53 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 Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: src/deep_researcher/gateway.py:history, src/deep_researcher/gateway.py:status 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 Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: scripts/live_e2e_experiment.py:main, scripts/live_e2e.py:main, scripts/live_e2e_parallel.py:main 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 se…

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places

Functions with the same first-5-line body hash: src/deep_researcher/storage/artifact_service.py:save_artifact, src/deep_researcher/storage/artifact_service.py:load_artifact, src/deep_researcher/storage/artifact_service.py:list_versions, src/deep_researcher/storage/artifact_service.py:list_artifact_…

duplicatesduplication

low System graph software Dead code conf 1.00 Possibly dead Python function: notify

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

src/deep_researcher/notify.py:19

low System graph software Dead code conf 1.00 Possibly dead Python function: tolerant_parse

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

src/deep_researcher/patches.py:40

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 /api/projects/{project_id}

`src/deep_researcher/gateway.py` declares `DELETE /api/projects/{project_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/dashboard

`src/deep_researcher/gateway.py` declares `GET /api/dashboard` 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/projects

`src/deep_researcher/gateway.py` declares `GET /api/projects` 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/projects/{project_id}/artifacts

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/artifacts` 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 consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/{project_id}/artifacts/content

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/artifacts/content` 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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/{project_id}/artifacts/{artifact_id}/lineage

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/artifacts/{artifact_id}/lineage` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/{project_id}/board

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/board` 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: GET /api/projects/{project_id}/budget

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/budget` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/{project_id}/history

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/history` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/{project_id}/runs

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/runs` 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/projects/{project_id}/status

`src/deep_researcher/gateway.py` declares `GET /api/projects/{project_id}/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 consumes …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/projects

`src/deep_researcher/gateway.py` declares `POST /api/projects` 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/projects/{project_id}/resume

`src/deep_researcher/gateway.py` declares `POST /api/projects/{project_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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/projects/{project_id}/runs/{run_id}/kill

`src/deep_researcher/gateway.py` declares `POST /api/projects/{project_id}/runs/{run_id}/kill` 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 …

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/7a954ca2-652e-4f53-b92a-4c46711c0dd0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7a954ca2-652e-4f53-b92a-4c46711c0dd0/

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.