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

Sprntly/sprntly-app

https://github.com/Sprntly/sprntly-app · scanned 2026-06-16 00:20 UTC (2 months, 2 weeks ago)

328 raw signals (0 security + 328 graph)

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

Complete repo analysis

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

JSON
Combined
60.3
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 310 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 5 Medium 18 Low 108 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 310 Crowd 0 Layer: Software 20 Frontend 2 Hardware 3 Security 9 Cicd 1 Quality 225 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 60.3/100 with 100.0% coverage. It contains 9269 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 328 findings — concentrated in quality (241), api (50), software (20). Risk profile is high: 0 critical, 5 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 131 of 310 actionable findings. 328 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security auth conf 1.00 FastAPI POST `github_webhook` without auth dependency — backend/app/routes/connectors.py:1949
`@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/routes/connectors.py:1949 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_comment_public` without auth dependency — backend/app/routes/design_agent.py:2328
`@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/routes/design_agent.py:2328 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_passcode` without auth dependency — backend/app/routes/design_agent.py:1900
`@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/routes/design_agent.py:1900 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'exec_used' in web/app/components/screens/app/PrdScreen.tsx:418
Found a known-risky pattern (exec_used). Review and replace if possible.
web/app/components/screens/app/PrdScreen.tsx:418 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in web/app/components/shared/PrdPanelContent.tsx:69
Found a known-risky pattern (exec_used). Review and replace if possible.
web/app/components/shared/PrdPanelContent.tsx:69 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ds-agent/ds_agent/server/static/app.js:206
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 — web/app/lib/api.ts:1010
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: backend/skills/negotiation-prep/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.
backend/skills/negotiation-prep/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/skills/saas-metrics-diagnosis/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.
backend/skills/saas-metrics-diagnosis/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/skills/stakeholder-update/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.
backend/skills/stakeholder-update/SKILL.md VerificationSkill file
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 hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
appleboy/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/deploy-agent.yml:24
.github/workflows/deploy-backend.yml:59
.github/workflows/sync-backend-env.yml:23
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ds-agent/ds_agent/server/static/app.js:125
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ds-agent/ds_agent/server/static/app.js:125 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/app/components/screens/app/PrdScreen.tsx:136
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/app/components/screens/app/PrdScreen.tsx:136 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/app/components/shared/PrdPanelContent.tsx:298
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/app/components/shared/PrdPanelContent.tsx:298 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/public/sprntly.js:22
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/public/sprntly.js:22 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/connectors/github_app.py:115
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/connectors/hubspot_oauth.py:141
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/connectors/slack_oauth.py:300
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/design_agent/storage.py:53
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 187 placeholder/mock markers across 87 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 17 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_COOKIE_SECRET`, `AGENT_EFFORT`, `AGENT_MAX_TOKENS`, `AGENT_MODEL`, `AGENT_PASSWORD`, `AGENT_UPLOAD_DIR`, `DESIGN_AGENT_ENABLED`, `DESIGN_AGENT_MAX_TOKENS` + 9 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't …
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 31 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: 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.
backend/Dockerfile:1 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/app/components/screens/app/TicketsScreen.tsx:157
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/public/sprntly.js:111
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/llm.py:call_json, backend/app/llm.py:call_md 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/design_agent/codebase_map/stack.py:enumerate_nodes, backend/app/design_agent/codebase_map/stack.py:enumerate_nodes, backend/app/design_agent/codebase_map/stack.py:enumerate_nodes This is *the* AI-coder failure mode (4× more duplication in…
5 occurrences
repo-level (5 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: backend/app/connectors/hubspot_oauth.py:sign_oauth_state, backend/app/connectors/figma_oauth.py:sign_oauth_state, backend/app/connectors/github_app.py:sign_oauth_state, backend/app/connectors/clickup_oauth.py:sign_oauth_state This is *the* AI-coder f…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/app/design_agent/design_system/github_gather.py:detect, backend/app/design_agent/design_system/github_gather.py:detect, backend/app/design_agent/design_system/github_gather.py:detect, backend/app/design_agent/design_system/github_gather.py:det…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `hubspot_env_v1` in backend/tests/test_routes_connectors_hubspot.py:57
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 `metric_series_v1` in backend/app/graph/config_layers.py:114
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 `pid_v2` in backend/tests/test_db_prototypes.py:290
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 `prd_v2` in backend/tests/test_design_agent_brief_prototype_map.py:235
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 `Sprntly_Onboarding_Flow_Spec_v1` in backend/app/connectors/fireflies_apikey.py:9
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 `Sprntly_Onboarding_Flow_Spec_v1` in backend/app/db/team.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 `Sprntly_Onboarding_Flow_Spec_v1` in backend/app/routes/team.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 `Sprntly_Onboarding_Flow_Spec_v1` in web/app/components/screens/app/settings/TeamSettings.tsx: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 `test_collect_edits_drops_noop_when_new_equals_old` in web/app/components/design-agent/__tests__/ManualEditOverlay.test.tsx:161
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_get_installation_for_company_rejects_foreign_and_legacy` in backend/tests/test_github_tenant_scope.py:133
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: clear_entities
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/db/knowledge.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_generate_brief
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/cli.py:24
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_init_db
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/cli.py:11
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_show_brief
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/cli.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: csv_to_md
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ingest.py:101
low System graph software Dead code conf 1.00 Possibly dead Python function: format_brief_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/connectors/slack_oauth.py:344
low System graph software Dead code conf 1.00 Possibly dead Python function: gc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ds-agent/ds_agent/server/state.py:81
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_risk_analysis_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/agents/risk_analysis.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_technical_design_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/agents/technical_design.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_traceability_matrix_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/agents/traceability_matrix.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: guarded_redirect_hook
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/net_guard.py:101
low System graph software Dead code conf 1.00 Possibly dead Python function: is_valid_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ds-agent/ds_agent/server/agents.py:210
low System graph software Dead code conf 1.00 Possibly dead Python function: model_post_init
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/routes/connectors.py:1763
low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_user_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/connectors/github_app.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: require_company_from_query
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:384
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_company_optional
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:397
low System graph software Dead code conf 1.00 Possibly dead Python function: scrape_multiple
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/agents/scraper.py:151
low System graph software Dead code conf 1.00 Possibly dead Python function: set_verify
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/qa_agent.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: upsert_entity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/db/knowledge.py:9
low System graph software Dead code conf 1.00 Possibly dead Python function: upsert_relationship
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/db/knowledge.py:34
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 /invites/{invite_id}
`backend/app/routes/team.py` declares `DELETE /invites/{invite_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 /members/{user_id}
`backend/app/routes/team.py` declares `DELETE /members/{user_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 /{conversation_id}
`backend/app/routes/conversations.py` declares `DELETE /{conversation_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 /{slug}
`backend/app/routes/datasets.py` declares `DELETE /{slug}` 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 /{slug}/files/{filename}
`backend/app/routes/datasets.py` declares `DELETE /{slug}/files/{filename}` 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 /{ticket_key}/attachments/{attachment_id}
`backend/app/routes/tickets.py` declares `DELETE /{ticket_key}/attachments/{attachment_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{ticket_key}/comments/{comment_id}
`backend/app/routes/tickets.py` declares `DELETE /{ticket_key}/comments/{comment_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: GET /
`backend/app/routes/backlog.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 /doc/{doc_id}
`backend/app/routes/multi_agent.py` declares `GET /doc/{doc_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 /export
`backend/app/routes/metrics.py` declares `GET /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /invites
`backend/app/routes/team.py` declares `GET /invites` 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 /latest
`backend/app/routes/prd.py` declares `GET /latest` 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 /me
`backend/app/auth.py` declares `GET /me` 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 /members
`backend/app/routes/team.py` declares `GET /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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /series
`backend/app/routes/metrics.py` declares `GET /series` 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 /skills
`backend/app/routes/ask.py` declares `GET /skills` 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 /usage
`backend/app/routes/ask.py` declares `GET /usage` 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 /{conversation_id}/turns
`backend/app/routes/conversations.py` declares `GET /{conversation_id}/turns` 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 /{evidence_id}
`backend/app/routes/evidence.py` declares `GET /{evidence_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 /{prd_id}
`backend/app/routes/prd.py` declares `GET /{prd_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 /{prd_id}/versions
`backend/app/routes/prd.py` declares `GET /{prd_id}/versions` 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}
`backend/app/routes/multi_agent.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}/docs
`backend/app/routes/multi_agent.py` declares `GET /{run_id}/docs` 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 /{slug}/files
`backend/app/routes/datasets.py` declares `GET /{slug}/files` 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 /{ticket_key}/data
`backend/app/routes/tickets.py` declares `GET /{ticket_key}/data` 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 /members/{user_id}
`backend/app/routes/team.py` declares `PATCH /members/{user_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 /{conversation_id}
`backend/app/routes/conversations.py` declares `PATCH /{conversation_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 /{item_id}
`backend/app/routes/backlog.py` declares `PATCH /{item_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`backend/app/routes/datasets.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 /accept
`backend/app/routes/team.py` declares `POST /accept` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /brief
`backend/app/routes/synthesis.py` declares `POST /brief` 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 /generate
`backend/app/routes/evidence.py` declares `POST /generate` 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 /invites
`backend/app/routes/team.py` declares `POST /invites` 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 /invites/{invite_id}/resend
`backend/app/routes/team.py` declares `POST /invites/{invite_id}/resend` 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 /lists
`backend/app/routes/stories.py` declares `POST /lists` 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 /login
`backend/app/auth.py` declares `POST /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 /logout
`backend/app/auth.py` declares `POST /logout` 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 /push
`backend/app/routes/stories.py` declares `POST /push` 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 /push-clickup
`backend/app/routes/tickets.py` declares `POST /push-clickup` 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 /refresh
`backend/app/routes/metrics.py` declares `POST /refresh` 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 /seed
`backend/app/routes/synthesis.py` declares `POST /seed` 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 /{conversation_id}/turns
`backend/app/routes/conversations.py` declares `POST /{conversation_id}/turns` 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 /{prd_id}/versions
`backend/app/routes/prd.py` declares `POST /{prd_id}/versions` 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 /{prd_id}/versions/{version_id}/restore
`backend/app/routes/prd.py` declares `POST /{prd_id}/versions/{version_id}/restore` 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 /{slug}/files
`backend/app/routes/datasets.py` declares `POST /{slug}/files` 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 /{slug}/generate
`backend/app/routes/datasets.py` declares `POST /{slug}/generate` 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 /{ticket_key}/attachments
`backend/app/routes/tickets.py` declares `POST /{ticket_key}/attachments` 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 /{ticket_key}/comments
`backend/app/routes/tickets.py` declares `POST /{ticket_key}/comments` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{prd_id}
`backend/app/routes/prd.py` declares `PUT /{prd_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: PUT /{ticket_key}/description
`backend/app/routes/tickets.py` declares `PUT /{ticket_key}/description` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/app/design_agent/codebase_map/recreate.py (1742 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/design_agent/design_system/adapters.py (1189 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/design_agent/prompts.py (961 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/design_agent/runner.py (1865 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/design_agent/storage.py (1144 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/routes/connectors.py (1978 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/routes/design_agent.py (3416 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/test_codebase_map_recreate.py (1825 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/test_design_agent_routes.py (1258 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/test_design_agent_storage.py (1255 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/test_design_system_figma_gather.py (1534 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/app/components/design-agent/PostGenerationResult.tsx (1689 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/app/components/screens/app/ChatScreen.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: web/app/components/shared/BriefChat.tsx (1715 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/app/components/shared/ContentPanel.tsx (1239 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/app/lib/api.ts (1557 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/daf129f9-af2c-4b86-964f-e1a9745fd5bf/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/daf129f9-af2c-4b86-964f-e1a9745fd5bf/

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.