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

sebo-b/warp

https://github.com/sebo-b/warp · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

140 raw signals (0 security + 140 graph)

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

Complete repo analysis

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

JSON
Combined
55.1
/100
Security checks
55
0 findings
System graph
55
100.0% cov · 126 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 28 Medium 21 Low 60 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 126 Crowd 0 Layer: Software 6 Frontend 7 Hardware 3 Security 40 Cicd 3 Quality 20 Api 47
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 55.1/100 with 100.0% coverage. It contains 683 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 140 findings — concentrated in api (47), security (43), quality (20). Risk profile is high: 7 critical, 28 high, 28 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 113 of 126 actionable findings. 140 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 e2e/helpers/admin.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
e2e/helpers/admin.ts:25
critical System graph security Secrets conf 1.00 Possible secret in e2e/helpers/db.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
e2e/helpers/db.ts:23
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in e2e/helpers/users.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 10, 12, 13, 14
e2e/helpers/users.ts:10, 12, 13, 14 (4 hits)
critical System graph security Secrets conf 1.00 Possible secret in warp/config.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
warp/config.py:119
high System graph api Wiring conf 1.00 Dangling fetch: GET /xhr/calendar (js/base/base.js:449)
`js/base/base.js:449` calls `GET /xhr/calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/xhr/calendar` 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: GET /xhr/prefs (js/base/base.js:127)
`js/base/base.js:127` calls `GET /xhr/prefs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/xhr/prefs` 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 /xhr/calendar (js/base/base.js:462)
`js/base/base.js:462` calls `POST /xhr/calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/xhr/calendar` 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 /xhr/calendar (js/base/base.js:484)
`js/base/base.js:484` calls `POST /xhr/calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/xhr/calendar` 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 /xhr/prefs (js/base/base.js:149)
`js/base/base.js:149` calls `POST /xhr/prefs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/xhr/prefs` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph security auth conf 1.00 Flask mutation route `addOrEdit` without `@login_required` — warp/xhr/plans.py:115
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/plans.py:115 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `addOrEdit` without `@login_required` — warp/xhr/zones.py:154
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zones.py:154 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `apply` without `@login_required` — warp/xhr/zone.py:274
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zone.py:274 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `assign` without `@login_required` — warp/xhr/groups.py:71
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/groups.py:71 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `assign` without `@login_required` — warp/xhr/zones.py:242
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zones.py:242 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `autoBook` without `@login_required` — warp/xhr/zone.py:849
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zone.py:849 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `calendar_post` without `@login_required` — warp/xhr/calendar.py:83
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/calendar.py:83 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `delete` without `@login_required` — warp/xhr/plans.py:87
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/plans.py:87 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `delete` without `@login_required` — warp/xhr/users.py:140
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/users.py:140 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `delete` without `@login_required` — warp/xhr/zones.py:89
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zones.py:89 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `edit` without `@login_required` — warp/xhr/users.py:54
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/users.py:54 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `listW` without `@login_required` — warp/xhr/bookings.py:50
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/bookings.py:50 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `listW` without `@login_required` — warp/xhr/plans.py:16
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/plans.py:16 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `listW` without `@login_required` — warp/xhr/users.py:11
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/users.py:11 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `listW` without `@login_required` — warp/xhr/zones.py:15
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zones.py:15 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `login` without `@login_required` — warp/auth_ldap.py:170
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/auth_ldap.py:170 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `login` without `@login_required` — warp/auth_oidc.py:92
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/auth_oidc.py:92 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `members` without `@login_required` — warp/xhr/groups.py:17
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/groups.py:17 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `members` without `@login_required` — warp/xhr/zones.py:197
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/zones.py:197 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `modify` without `@login_required` — warp/xhr/plans.py:179
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/plans.py:179 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `prefs_set` without `@login_required` — warp/xhr/prefs.py:78
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/prefs.py:78 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `report` without `@login_required` — warp/xhr/bookings.py:13
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/xhr/bookings.py:13 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `set_time_offset` without `@login_required` — warp/debug.py:20
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
warp/debug.py:20 securityAuth flask unauth route
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — e2e/fixtures.ts:12
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 — js/base/base.js:149
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 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 Supply chain conf 1.00 2 occurrences Docker base image uses a mutable or implicit tag: alpine:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 25
containers/Dockerfile:1, 25 (2 hits)
containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: containers/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 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/metadata-action@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 40, 45, 52, 56, 112, 119, 123
.github/workflows/containers.yml:40, 45, 52, 56, 112, 119, 123 (7 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/containers.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/base/base.js:243
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/base/base.js:243 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/groupAssign.js:105
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/groupAssign.js:105 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/modules/modal.js:33
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/modules/modal.js:33 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/modules/zoneModify_marquee.js:90
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/modules/zoneModify_marquee.js:90 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/planModify.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/planModify.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/users.js:98
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/users.js:98 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/zone.js:459
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/zone.js:459 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/views/zones.js:160
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/views/zones.js:160 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in warp/static/materialize/materialize.min.js:6
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
warp/static/materialize/materialize.min.js:6 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in warp/static/materialize/materialize.min.js:6
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
warp/static/materialize/materialize.min.js:6 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in e2e/global-setup.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
e2e/global-setup.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in e2e/global-teardown.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
e2e/global-teardown.ts:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — setup.py:14
`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 23 placeholder/mock markers across 4 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 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 36 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 cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 5 locations
.github/workflows/containers.yml:73, 105 (2 hits)
.github/workflows/e2e.yml:15, 40 (2 hits)
.github/workflows/main.yml:9
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'document_write' in js/base/base.js:46
Found a known-risky pattern (document_write). Review and replace if possible.
js/base/base.js:46 Document write
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: warp/auth.py:loginMatch, warp/auth.py:login 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.
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: warp/xhr/plans.py:addOrEdit, warp/xhr/zones.py:addOrEdit, warp/xhr/zones.py:assign 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.
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cal_copy` in js/base/base.js:195
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 `tooOld` in e2e/tests/settings/calendar.spec.ts:175
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_app
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/__init__.py:5
low System graph software Dead code conf 1.00 Possibly dead Python function: formatTimestamp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/utils.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: funOperator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/xhr/bookings.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: inner
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/utils.py:96
low System graph software Dead code conf 1.00 Possibly dead Python function: parse
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/config.py:170
low System graph software Dead code conf 1.00 Possibly dead Python function: session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
warp/auth.py:150
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 — e2e/global-setup.ts:60
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 — e2e/global-teardown.ts:16
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 — js/webpack.config.js:24
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 api Wiring conf 1.00 Unused endpoint: ANY /
`warp/view.py` declares `ANY /` 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: ANY /addoredit
`warp/xhr/plans.py` declares `ANY /addoredit` 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: ANY /allZones
`warp/xhr/plans.py` declares `ANY /allZones` 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: ANY /apply
`warp/xhr/zone.py` declares `ANY /apply` 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: ANY /assign
`warp/xhr/groups.py` declares `ANY /assign` 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: ANY /autoBook/<int:pid>
`warp/xhr/zone.py` declares `ANY /autoBook/<int:pid>` 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: ANY /bookings
`warp/view.py` declares `ANY /bookings` 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: ANY /bookings/<string:report>
`warp/view.py` declares `ANY /bookings/<string:report>` 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: ANY /calendar
`warp/xhr/calendar.py` declares `ANY /calendar` 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: ANY /calendar/<login>/book
`warp/ical.py` declares `ANY /calendar/<login>/book` 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: ANY /calendar/<login>/delete
`warp/ical.py` declares `ANY /calendar/<login>/delete` 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: ANY /calendar/<login>/events.ics
`warp/ical.py` declares `ANY /calendar/<login>/events.ics` 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: ANY /calendar/cancelled
`warp/ical.py` declares `ANY /calendar/cancelled` 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: ANY /debug/endpoints
`warp/debug.py` declares `ANY /debug/endpoints` 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: ANY /debug/set_time_offset
`warp/debug.py` declares `ANY /debug/set_time_offset` 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: ANY /debug/time
`warp/debug.py` declares `ANY /debug/time` 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: ANY /delete
`warp/xhr/plans.py` declares `ANY /delete` 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: ANY /edit
`warp/xhr/users.py` declares `ANY /edit` 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: ANY /getSeats/<int:pid>
`warp/xhr/plans.py` declares `ANY /getSeats/<int:pid>` 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: ANY /getUsers/<int:pid>
`warp/xhr/zone.py` declares `ANY /getUsers/<int:pid>` 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: ANY /groups
`warp/view.py` declares `ANY /groups` 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: ANY /groups/<login>
`warp/xhr/users.py` declares `ANY /groups/<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: ANY /groups/assign/<group_login>
`warp/view.py` declares `ANY /groups/assign/<group_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: ANY /list
`warp/xhr/plans.py` declares `ANY /list` 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: ANY /login
`warp/auth_aad.py` declares `ANY /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: ANY /logout
`warp/auth_mellon.py` declares `ANY /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: ANY /members
`warp/xhr/groups.py` declares `ANY /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: ANY /modify
`warp/xhr/plans.py` declares `ANY /modify` 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: ANY /names
`warp/xhr/zones.py` declares `ANY /names` 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: ANY /oidc/callback
`warp/auth_oidc.py` declares `ANY /oidc/callback` 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: ANY /oidc/start
`warp/auth_oidc.py` declares `ANY /oidc/start` 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: ANY /plan/<pid>
`warp/view.py` declares `ANY /plan/<pid>` 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: ANY /plan/image/<pid>
`warp/view.py` declares `ANY /plan/image/<pid>` 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: ANY /plans
`warp/view.py` declares `ANY /plans` 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: ANY /plans/modify/<pid>
`warp/view.py` declares `ANY /plans/modify/<pid>` 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: ANY /prefs
`warp/xhr/prefs.py` declares `ANY /prefs` 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: ANY /report
`warp/xhr/bookings.py` declares `ANY /report` 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: ANY /signin-oidc
`warp/auth_aad.py` declares `ANY /signin-oidc` 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: ANY /users
`warp/view.py` declares `ANY /users` 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: ANY /zones
`warp/view.py` declares `ANY /zones` 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: ANY /zones/assign/<zid>
`warp/view.py` declares `ANY /zones/assign/<zid>` 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: ANY /zonesForPlan
`warp/xhr/plans.py` declares `ANY /zonesForPlan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/59db239e-5a42-420a-b9e4-a4076e31d204/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/59db239e-5a42-420a-b9e4-a4076e31d204/

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.