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

statyk/compendium

https://github.com/statyk/compendium · scanned 2026-06-16 00:21 UTC (2 months, 2 weeks ago)

152 raw signals (7 security + 145 graph)

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

Complete repo analysis

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

JSON
Combined
69.7
/100
Security checks
70
4 findings
System graph
70
100.0% cov · 121 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 10 Medium 9 Low 93 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 4 System graph 121 Crowd 0 Layer: Quality 48 Software 8 Frontend 3 Hardware 2 Security 11 Cicd 3 Api 50
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.7/100 with 100.0% coverage. It contains 6451 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 145 findings — concentrated in quality (60), api (50), security (11). Risk profile is high: 0 critical, 8 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 112 of 125 actionable findings. 154 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 Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: statyk/compendium
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
2 occurrences
repo-level (2 hits)
high Security checks quality Testing conf 0.78 Foundry mined test ci gap after feedback: statyk/compendium
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
high System graph security auth conf 1.00 FastAPI POST `edit_pending_save` without auth dependency — src/compendium/web/routes/scan.py:890
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/scan.py:890 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_submit` without auth dependency — src/compendium/web/routes/bulk.py:268
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/bulk.py:268 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `item_create_manual` without auth dependency — src/compendium/web/routes/items.py:288
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/items.py:288 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `patron_create` without auth dependency — src/compendium/web/routes/patrons.py:144
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/patrons.py:144 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `policy_update` without auth dependency — src/compendium/web/routes/policies.py:138
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/policies.py:138 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `user_create` without auth dependency — src/compendium/web/routes/users.py:129
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/users.py:129 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `work_edit_submit` without auth dependency — src/compendium/web/routes/catalog.py:380
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/compendium/web/routes/catalog.py:380 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/compendium/web/static/htmx.min.js:1
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/compendium/web/static/htmx.min.js:1 New function used
medium Security checks quality Practices conf 0.62 3 occurrences Foundry mined assumption checks: statyk/compendium
Comment chain pattern product: assumption_checks Repo: statyk/compendium Thread: statyk/compendium#3 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_…
3 occurrences
repo-level (3 hits)
medium Security checks quality maintenance conf 0.70 3 occurrences Foundry mined blueprint gap alignment: statyk/compendium
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
3 occurrences
repo-level (3 hits)
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 cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 33, 39, 52, 55, 58, 66, 75, 101
.github/workflows/release.yml:33, 39, 52, 55, 58, 66, 75, 101 (8 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/compendium/web/static/htmx.min.js:1
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/compendium/web/static/htmx.min.js:1 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/compendium/web/static/htmx.min.js:1
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/compendium/web/static/htmx.min.js:1 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in src/compendium/web/static/htmx.min.js:1
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
src/compendium/web/static/htmx.min.js:1 Insert adjacent html
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/render_label_matrix.py:71
`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
low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `COMPENDIUM_ACTOR_USERNAME`, `COMPENDIUM_ALLOW_INSECURE_JWT`, `COMPENDIUM_COVER_CACHE_DIR`, `COMPENDIUM_DATABASE_URL`, `COMPENDIUM_MATRIX_ADMIN_PASS`, `COMPENDIUM_MATRIX_ADMIN_USER`, `COMPENDIUM_SCAFFOLD_DIR`, `COMPENDIUM_SECRET_KEY` + 1 more. Add …
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 16 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-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, 23
docker/Dockerfile:2, 23 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 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.
.github/workflows/release.yml:28 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 12 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/compendium/api/deps.py:get_calendar_svc, src/compendium/web/deps.py:get_calendar_svc 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.
12 occurrences
repo-level (12 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/compendium/web/routes/admin_settings.py:general_get, src/compendium/web/routes/admin_settings.py:circulation_get, src/compendium/web/routes/admin_settings.py:kiosk_get This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos —…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/compendium/web/routes/fines.py:verify_returned_confirm_form, src/compendium/web/routes/fines.py:verify_returned, src/compendium/web/routes/fines.py:write_off_claim_form, src/compendium/web/routes/fines.py:write_off_claim This is *the* AI-coder fa…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: src/compendium/cli/commands/labels.py:spine_labels, src/compendium/cli/commands/labels.py:pocket_labels, src/compendium/cli/commands/labels.py:barcode_labels, src/compendium/cli/commands/labels.py:patron_card This is *the* AI-coder failure mode (4× m…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `added_copy` in src/compendium/services/catalog.py:1063
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 `added_copy` in src/compendium/services/import_export.py:509
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 `added_copy` in tests/integration/test_import_export_api.py:217
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 `added_copy` in tests/integration/test_import_export_lt.py:146
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 `available_copy` in tests/unit/test_hold_service.py:34
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 `first_available_loanable_copy` in src/compendium/repositories/base.py:99
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 `first_available_loanable_copy` in src/compendium/repositories/sql/work_repository.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 `first_available_loanable_copy` in src/compendium/services/holds.py:125
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 `ReturnOld` in tests/integration/test_discovery.py:209
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 `t_old` in tests/integration/test_item_note_model.py:82
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 `t_old` in tests/unit/test_item_note_repository.py:107
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_add_item_to_work_adds_copy` in tests/integration/test_catalog.py:92
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_checkout_by_isbn_skips_checked_out_copy` in tests/integration/test_isbn_circulation.py:109
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_delete_older_than_noop_when_nothing_old` in tests/integration/test_audit_prune.py:75
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_no_stale_code128_default_copy` in tests/integration/test_labels_web.py:383
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_place_hold_succeeds_with_one_loanable_copy` in tests/integration/test_holds.py:143
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_role_clone_creates_editable_copy` in tests/integration/test_web_ui.py:1558
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: backup_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/cli/commands/backup.py:12
low System graph software Dead code conf 1.00 Possibly dead Python function: init_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/cli/commands/init.py:12
low System graph software Dead code conf 1.00 Possibly dead Python function: list_users
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/services/auth.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: render_patron_label_svg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/services/labels.py:1124
low System graph software Dead code conf 1.00 Possibly dead Python function: require_scan_pairing
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/web/deps.py:128
low System graph software Dead code conf 1.00 Possibly dead Python function: require_web_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/web/deps.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: restore_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/cli/commands/backup.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_google_books_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/compendium/services/metadata.py:1083
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 — src/compendium/web/static/htmx.min.js:1
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 — src/compendium/web/static/zxing/zxing-browser.min.js:1
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 quality Integrity conf 1.00 Stub function `_main` (body is just `pass`/`return`) — src/compendium/cli/main.py:51
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /closed-dates/{closed_date_id}
`src/compendium/api/routes/calendar.py` declares `DELETE /closed-dates/{closed_date_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /households/{household_id}
`src/compendium/api/routes/households.py` declares `DELETE /households/{household_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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /households/{household_id}/members/{card_number}
`src/compendium/api/routes/households.py` declares `DELETE /households/{household_id}/members/{card_number}` 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: DELETE /items/{barcode}/notes/{note_id}
`src/compendium/api/routes/items.py` declares `DELETE /items/{barcode}/notes/{note_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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /patron-categories/{category_id}
`src/compendium/api/routes/patron_categories.py` declares `DELETE /patron-categories/{category_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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`src/compendium/api/routes/notifications.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 /branches/
`src/compendium/api/routes/branches.py` declares `GET /branches/` 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 /closed-dates/
`src/compendium/api/routes/calendar.py` declares `GET /closed-dates/` 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 /fines
`src/compendium/api/routes/fines.py` declares `GET /fines` 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 /households
`src/compendium/api/routes/households.py` declares `GET /households` 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 /households/{household_id}
`src/compendium/api/routes/households.py` declares `GET /households/{household_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /items/{barcode}
`src/compendium/api/routes/items.py` declares `GET /items/{barcode}` 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 /items/{barcode}/notes
`src/compendium/api/routes/items.py` declares `GET /items/{barcode}/notes` 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 /library-hours/
`src/compendium/api/routes/calendar.py` declares `GET /library-hours/` 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 /loans
`src/compendium/api/routes/loans.py` declares `GET /loans` 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 /loans/item/{barcode}
`src/compendium/api/routes/loans.py` declares `GET /loans/item/{barcode}` 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 /loans/patron/{card_number}
`src/compendium/api/routes/loans.py` declares `GET /loans/patron/{card_number}` 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 /patron-categories/
`src/compendium/api/routes/patron_categories.py` declares `GET /patron-categories/` 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: GET /reports/checkouts
`src/compendium/api/routes/reports.py` declares `GET /reports/checkouts` 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 /reports/dormant
`src/compendium/api/routes/reports.py` declares `GET /reports/dormant` 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 /reports/overdues
`src/compendium/api/routes/reports.py` declares `GET /reports/overdues` 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 /reports/popular
`src/compendium/api/routes/reports.py` declares `GET /reports/popular` 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 /{card_number}/fines
`src/compendium/api/routes/fines.py` declares `GET /{card_number}/fines` 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 /branches/{branch_id}
`src/compendium/api/routes/branches.py` declares `PATCH /branches/{branch_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 /closed-dates/{closed_date_id}
`src/compendium/api/routes/calendar.py` declares `PATCH /closed-dates/{closed_date_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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /creators/{creator_id}
`src/compendium/api/routes/creators.py` declares `PATCH /creators/{creator_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 /households/{household_id}
`src/compendium/api/routes/households.py` declares `PATCH /households/{household_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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /items/{barcode}
`src/compendium/api/routes/items.py` declares `PATCH /items/{barcode}` 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 /library-hours/{weekday}
`src/compendium/api/routes/calendar.py` declares `PATCH /library-hours/{weekday}` 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: PATCH /patron-categories/{category_id}
`src/compendium/api/routes/patron_categories.py` declares `PATCH /patron-categories/{category_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`src/compendium/api/routes/fines.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 /auth/login
`src/compendium/api/routes/auth.py` declares `POST /auth/login` 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 /closed-dates/
`src/compendium/api/routes/calendar.py` declares `POST /closed-dates/` 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 /households
`src/compendium/api/routes/households.py` declares `POST /households` 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 /households/{household_id}/members
`src/compendium/api/routes/households.py` declares `POST /households/{household_id}/members` 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 /items/{barcode}/clear-damage
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/clear-damage` 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 /items/{barcode}/clear-lost
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/clear-lost` 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 /items/{barcode}/damaged
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/damaged` 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 /items/{barcode}/loanable
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/loanable` 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 /items/{barcode}/lost
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/lost` 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 /items/{barcode}/notes
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/notes` 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 /items/{barcode}/withdraw
`src/compendium/api/routes/items.py` declares `POST /items/{barcode}/withdraw` 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 /loans/checkout
`src/compendium/api/routes/loans.py` declares `POST /loans/checkout` 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 /loans/{loan_id}/checkin
`src/compendium/api/routes/loans.py` declares `POST /loans/{loan_id}/checkin` 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 /loans/{loan_id}/renew
`src/compendium/api/routes/loans.py` declares `POST /loans/{loan_id}/renew` 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 /patron-categories/
`src/compendium/api/routes/patron_categories.py` declares `POST /patron-categories/` 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: POST /{card_number}/fines/assess-overdue
`src/compendium/api/routes/fines.py` declares `POST /{card_number}/fines/assess-overdue` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{fine_id}/pay
`src/compendium/api/routes/fines.py` declares `POST /{fine_id}/pay` 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 /{fine_id}/waive
`src/compendium/api/routes/fines.py` declares `POST /{fine_id}/waive` 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 /{notification_id}/retry
`src/compendium/api/routes/notifications.py` declares `POST /{notification_id}/retry` 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 quality Complexity conf 1.00 Very large file: src/compendium/services/catalog.py (1300 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/compendium/services/import_export.py (1621 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/test_cli_commands.py (1804 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/test_web_ui.py (2001 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/test_labels_service.py (1758 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/b72a777a-78f2-4948-8479-da8a81a22b70/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b72a777a-78f2-4948-8479-da8a81a22b70/

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.