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

raphaelfh/prumo

https://github.com/raphaelfh/prumo · scanned 2026-06-15 23:47 UTC (2 months, 4 weeks ago)

284 raw signals (0 security + 284 graph)

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

Complete repo analysis

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

JSON
Combined
43.4
/100
Security checks
43
0 findings
System graph
43
100.0% cov · 241 findings
Critical
4
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 4 High 17 Medium 31 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 241 Crowd 0 Layer: Software 12 Frontend 32 Hardware 4 Security 22 Cicd 2 Quality 129 Api 40
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 43.4/100 with 100.0% coverage. It contains 6159 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 284 findings — concentrated in quality (149), api (40), frontend (32). Risk profile is high: 9 critical, 17 high, 40 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 132 of 241 actionable findings. 284 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 System graph security Secrets conf 1.00 Possible secret in frontend/e2e/_fixtures/fixture-ids.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/e2e/_fixtures/fixture-ids.ts:8
critical System graph security Secrets conf 1.00 Possible secret in frontend/e2e/flows/settings-api-keys.e2e.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
frontend/e2e/flows/settings-api-keys.e2e.ts:33
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in frontend/lib/copy/auth.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 14, 47, 48, 62
frontend/lib/copy/auth.ts:14, 47, 48, 62 (4 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in frontend/lib/copy/user.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 54, 55, 61
frontend/lib/copy/user.ts:54, 55, 61 (3 hits)
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/errors (frontend/services/errorTracking.ts:227)
`frontend/services/errorTracking.ts:227` calls `POST /api/errors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/errors` 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 /api/metrics (frontend/services/errorTracking.ts:243)
`frontend/services/errorTracking.ts:243` calls `POST /api/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/metrics` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
.devcontainer/Dockerfile:27 containersRemote installer
high System graph security auth conf 1.00 FastAPI DELETE `cancel_export` without auth dependency — backend/app/api/v1/endpoints/articles_export.py:335
`@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/endpoints/articles_export.py:335 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `cancel_extraction_export` without auth dependency — backend/app/api/v1/endpoints/extraction_export.py:449
`@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/endpoints/extraction_export.py:449 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_api_key` without auth dependency — backend/app/api/v1/endpoints/user_api_keys.py:301
`@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/endpoints/user_api_keys.py:301 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_api_key` without auth dependency — backend/app/api/v1/endpoints/user_api_keys.py:171
`@router.patch` 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/endpoints/user_api_keys.py:171 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cancel_export` without auth dependency — backend/app/api/v1/endpoints/articles_export.py:330
`@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/endpoints/articles_export.py:330 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cancel_extraction_export` without auth dependency — backend/app/api/v1/endpoints/extraction_export.py:444
`@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/endpoints/extraction_export.py:444 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_api_key` without auth dependency — backend/app/api/v1/endpoints/user_api_keys.py:105
`@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/endpoints/user_api_keys.py:105 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `extract_models` without auth dependency — backend/app/api/v1/endpoints/model_extraction.py:107
`@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/endpoints/model_extraction.py:107 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `extract_section` without auth dependency — backend/app/api/v1/endpoints/section_extraction.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.
backend/app/api/v1/endpoints/section_extraction.py:65 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_export` without auth dependency — backend/app/api/v1/endpoints/articles_export.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.
backend/app/api/v1/endpoints/articles_export.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_extraction_export` without auth dependency — backend/app/api/v1/endpoints/extraction_export.py:125
`@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/endpoints/extraction_export.py:125 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_feedback` without auth dependency — backend/app/api/v1/endpoints/feedback.py:18
`@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/endpoints/feedback.py:18 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_api_key` without auth dependency — backend/app/api/v1/endpoints/user_api_keys.py:355
`@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/endpoints/user_api_keys.py:355 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `zotero_action` without auth dependency — backend/app/api/v1/endpoints/zotero_import.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.
backend/app/api/v1/endpoints/zotero_import.py:91 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/api.ts:38
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/ensure-fixtures.ts:16
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/global-setup.ts:151
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/global-teardown.ts:19
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/storage.ts:4
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/_fixtures/supabase-admin.ts:29
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/e2e/extraction-observability.e2e.ts:37
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/services/apiKeysService.ts:66
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/services/articlesExportService.ts:58
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/services/errorTracking.ts:243
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/services/extractionExportService.ts:55
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/test/hooks/useExtractionSession.test.tsx:191
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 authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/architectural-quality-loop/references/budget-policy.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/architectural-quality-loop/references/budget-policy.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/architectural-quality-loop/references/concept-glossary.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/architectural-quality-loop/references/concept-glossary.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/backend-development/references/pydantic.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/backend-development/references/pydantic.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/backend-development/references/sqlalchemy.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/backend-development/references/sqlalchemy.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/backend-development/references/structlog.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/backend-development/references/structlog.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-review/references/automated-pr-review.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/code-review/references/automated-pr-review.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/frontend-ux/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/frontend-ux/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/ui-styling/references/tailwind-v4.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/ui-styling/references/tailwind-v4.md VerificationClaude instruction
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 4 occurrences Frontend route `/auth/reset-password` has no Link/navigate to it — frontend/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/projects/:projectId/articles/:articleId/quality-assessment/:templateId` has no Link/navigate to it — frontend/test/QualityAssessmentFullScreen.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/projects/:projectId` has no Link/navigate to it — frontend/test/QualityAssessmentInterface.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/setup-uv@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 7 locations
.github/workflows/ci.yml:39, 144, 317, 366, 436, 439 (6 hits)
.github/workflows/worker-smoke.yml:45
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/pdf-viewer/engines/mock/index.ts:114
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/pdf-viewer/engines/mock/index.ts:114 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/pdf-viewer/engines/pdfjs/page.ts:92
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/pdf-viewer/engines/pdfjs/page.ts:92 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/pdf-viewer/primitives/TextLayer.tsx:41
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/pdf-viewer/primitives/TextLayer.tsx:41 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 205 placeholder/mock markers across 74 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 Integrity conf 1.00 45 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `DEV`, `E2E_API_URL`, `E2E_ARTICLE_ID`, `E2E_AUTH_TOKEN`, `E2E_ENTITY_TYPE_ID`, `E2E_FRONTEND_URL`, `E2E_IMPORT_PROJECT_ID` + 37 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
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 58 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: node:20-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.devcontainer/Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-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, 19
backend/Dockerfile:2, 19 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 12 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 34, 78, 87, 139, 361, 456, 492, 559, +4 more
.github/workflows/ci.yml:34, 78, 87, 139, 361, 456, 492, 559, +4 more (12 hits)
CI/CD securitySupply chainGithub actions
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 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/fitness/check_api_response_envelope.py:scan_file, scripts/fitness/check_api_response_envelope.py:scan This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
13 occurrences
repo-level (13 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/fitness/check_react_query_keys.py:load_baseline, scripts/fitness/check_api_response_envelope.py:load_baseline, scripts/fitness/check_layered_arch.py:load_baseline This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — …
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: backend/app/services/extraction_consensus_service.py:record_consensus, backend/app/services/extraction_consensus_service.py:publish, backend/app/services/extraction_review_service.py:record_decision, backend/app/services/extraction_proposal_service.py…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `0001_baseline_v1` in backend/alembic/versions/0001_baseline_v1.py:3
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 `0001_baseline_v1` in backend/alembic/versions/0002_drop_extracted_values.py:4
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 `0001_baseline_v1` in backend/alembic/versions/0003_storage_object_policies.py:12
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 `0001_baseline_v1` in backend/app/models/article.py:313
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 `baseline_v1` in backend/alembic/versions/0007_drop_migration_status.py:7
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 `baseline_v1` in backend/tests/integration/test_migration_roundtrip.py:47
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 `baseline_v1` in scripts/fitness/check_legacy_concepts.py:97
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 `extraction_legacy` in backend/tests/unit/scripts/test_check_rls_coverage_canary.py:67
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 `extraction_run_stage_old` in backend/alembic/versions/archive/20260427_0014_run_stage_enum_migration.py:18
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 `useLegacy` in backend/tests/unit/scripts/test_check_react_query_keys_canary.py:69
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_from_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/repositories/base.py:171
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/domain/events/base.py:101
low System graph software Dead code conf 1.00 Possibly dead Python function: delete_by_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/repositories/base.py:251
low System graph software Dead code conf 1.00 Possibly dead Python function: invalidate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/core/security.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: list_by_reviewer_item
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/repositories/extraction_reviewer_decision_repository.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: list_files
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/infrastructure/storage/supabase_storage.py:215
low System graph software Dead code conf 1.00 Possibly dead Python function: load_dialect_impl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/models/base.py:115
low System graph software Dead code conf 1.00 Possibly dead Python function: register
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/domain/events/base.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: require_project_manager
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps/security.py:73
low System graph software Dead code conf 1.00 Possibly dead Python function: require_project_scope
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps/security.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: to_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/model_extraction_service.py:552
low System graph software Dead code conf 1.00 Possibly dead Python function: to_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/domain/events/base.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 /articles-export/status/{job_id}
`backend/app/api/v1/endpoints/articles_export.py` declares `DELETE /articles-export/status/{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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /projects/{project_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `DELETE /projects/{project_id}/hitl-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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /projects/{project_id}/templates/{project_template_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `DELETE /projects/{project_id}/templates/{project_template_id}/hitl-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 cod…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{key_id}
`backend/app/api/v1/endpoints/user_api_keys.py` declares `DELETE /{key_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: DELETE /{project_id}/extraction-export/status/{job_id}
`backend/app/api/v1/endpoints/extraction_export.py` declares `DELETE /{project_id}/extraction-export/status/{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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/app/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 /articles-export/status/{job_id}
`backend/app/api/v1/endpoints/articles_export.py` declares `GET /articles-export/status/{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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /articles/{article_id}/citations
`backend/app/api/v1/endpoints/citations.py` declares `GET /articles/{article_id}/citations` 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 /projects/{project_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `GET /projects/{project_id}/hitl-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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /projects/{project_id}/templates/{project_template_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `GET /projects/{project_id}/templates/{project_template_id}/hitl-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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /providers
`backend/app/api/v1/endpoints/user_api_keys.py` declares `GET /providers` 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 /{article_file_id}/text-blocks
`backend/app/api/v1/endpoints/article_text_blocks.py` declares `GET /{article_file_id}/text-blocks` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{project_id}/extraction-export/reviewers
`backend/app/api/v1/endpoints/extraction_export.py` declares `GET /{project_id}/extraction-export/reviewers` 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 /{project_id}/extraction-export/status/{job_id}
`backend/app/api/v1/endpoints/extraction_export.py` declares `GET /{project_id}/extraction-export/status/{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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{run_id}
`backend/app/api/v1/endpoints/extraction_runs.py` declares `GET /{run_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 /{run_id}/reviewers
`backend/app/api/v1/endpoints/extraction_runs.py` declares `GET /{run_id}/reviewers` 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 /{run_id}/view
`backend/app/api/v1/endpoints/extraction_runs.py` declares `GET /{run_id}/view` 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 /{key_id}
`backend/app/api/v1/endpoints/user_api_keys.py` declares `PATCH /{key_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: PATCH /{project_id}/templates/{template_id}
`backend/app/api/v1/endpoints/project_templates.py` declares `PATCH /{project_id}/templates/{template_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`backend/app/api/v1/endpoints/user_api_keys.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 /articles-export
`backend/app/api/v1/endpoints/articles_export.py` declares `POST /articles-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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /articles-export/status/{job_id}/cancel
`backend/app/api/v1/endpoints/articles_export.py` declares `POST /articles-export/status/{job_id}/cancel` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /extraction/models
`backend/app/api/v1/endpoints/model_extraction.py` declares `POST /extraction/models` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /extraction/models/manual
`backend/app/api/v1/endpoints/model_extraction.py` declares `POST /extraction/models/manual` 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: POST /extraction/sections
`backend/app/api/v1/endpoints/section_extraction.py` declares `POST /extraction/sections` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /hitl/sessions
`backend/app/api/v1/endpoints/hitl_sessions.py` declares `POST /hitl/sessions` 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 /zotero/{action}
`backend/app/api/v1/endpoints/zotero_import.py` declares `POST /zotero/{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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{key_id}/validate
`backend/app/api/v1/endpoints/user_api_keys.py` declares `POST /{key_id}/validate` 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 /{project_id}/extraction-export
`backend/app/api/v1/endpoints/extraction_export.py` declares `POST /{project_id}/extraction-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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{project_id}/extraction-export/status/{job_id}/cancel
`backend/app/api/v1/endpoints/extraction_export.py` declares `POST /{project_id}/extraction-export/status/{job_id}/cancel` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{project_id}/templates/clone
`backend/app/api/v1/endpoints/project_templates.py` declares `POST /{project_id}/templates/clone` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{run_id}/advance
`backend/app/api/v1/endpoints/extraction_runs.py` declares `POST /{run_id}/advance` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{run_id}/consensus
`backend/app/api/v1/endpoints/extraction_runs.py` declares `POST /{run_id}/consensus` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{run_id}/decisions
`backend/app/api/v1/endpoints/extraction_runs.py` declares `POST /{run_id}/decisions` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{run_id}/proposals
`backend/app/api/v1/endpoints/extraction_runs.py` declares `POST /{run_id}/proposals` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{run_id}/reopen
`backend/app/api/v1/endpoints/extraction_runs.py` declares `POST /{run_id}/reopen` 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: PUT /projects/{project_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `PUT /projects/{project_id}/hitl-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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /projects/{project_id}/templates/{project_template_id}/hitl-config
`backend/app/api/v1/endpoints/hitl_configs.py` declares `PUT /projects/{project_id}/templates/{project_template_id}/hitl-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 —…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/alembic/versions/archive/0001_initial_public_schema.py (2783 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/seed.py (1941 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/extraction_export_service.py (1521 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/unit/test_extraction_export_service.py (2193 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/unit/test_section_extraction_service.py (1818 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/articles/ArticleForm.tsx (1272 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/articles/ArticlesList.tsx (1364 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/extraction/ArticleExtractionTable.tsx (1198 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/integrations/supabase/types.ts (2423 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/types/api/schema.d.ts (4114 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/baa64971-68cb-4924-958a-06febe4d52bd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/baa64971-68cb-4924-958a-06febe4d52bd/

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.