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

sportiviforyou-netizen/jarvis-command-center

https://github.com/sportiviforyou-netizen/jarvis-command-center · scanned 2026-06-16 00:19 UTC (2 months, 2 weeks ago)

112 raw signals (0 security + 112 graph)

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

Complete repo analysis

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

JSON
Combined
62.2
/100
Security checks
62
0 findings
System graph
62
88.9% cov · 108 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 14 Medium 30 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 108 Crowd 0 Layer: Frontend 3 Security 22 Cicd 2 Quality 33 Api 48
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 62.2/100 with 88.9% coverage. It contains 823 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 112 findings — concentrated in api (48), quality (33), security (22). Risk profile is high: 0 critical, 14 high, 30 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 100 of 108 actionable findings. 112 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 api Wiring conf 1.00 Dangling fetch: GET http://localhost:${info.port}/status?token=${info.token} (sportivi-dashboard/.claude/skills/impeccable/scripts/live-status.mjs:16)
`sportivi-dashboard/.claude/skills/impeccable/scripts/live-status.mjs:16` calls `GET http://localhost:${info.port}/status?token=${info.token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/stat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${info.port}/stop?token=${info.token} (sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:734)
`sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:734` calls `GET http://localhost:${info.port}/stop?token=${info.token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/stop`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/design-system.json?token=${TOKEN} (sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:4146)
`sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:4146` calls `GET http://localhost:${PORT}/design-system.json?token=${TOKEN}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/design-system/raw?token=${TOKEN} (sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:4147)
`sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:4147` calls `GET http://localhost:${PORT}/design-system/raw?token=${TOKEN}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/d…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://jarvis-command-center-1-0.onrender.com/ping (sportivi-dashboard/src/App.jsx:468)
`sportivi-dashboard/src/App.jsx:468` calls `GET https://jarvis-command-center-1-0.onrender.com/ping` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/jarvis-command-center-1-0.onrender.com/ping` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${info.port}/poll (sportivi-dashboard/.claude/skills/impeccable/scripts/live-complete.mjs:60)
`sportivi-dashboard/.claude/skills/impeccable/scripts/live-complete.mjs:60` calls `POST http://localhost:${info.port}/poll` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/poll` If this points at…
Dangling fetchFetch
high System graph security auth conf 1.00 Flask mutation route `handle_command_stream` without `@login_required` — app.py:2006
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:2006 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `handle_command` without `@login_required` — app.py:2120
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:2120 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `jarvis_chat` without `@login_required` — app.py:3704
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:3704 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `link_register` without `@login_required` — app.py:2919
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:2919 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `trend_scan` without `@login_required` — app.py:1301
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:1301 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `trigger_affiliate` without `@login_required` — app.py:996
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:996 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `voice_transcribe` without `@login_required` — app.py:1481
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:1481 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `voice_tts` without `@login_required` — app.py:1504
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app.py:1504 securityAuth flask unauth route
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:1841
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 — sportivi-dashboard/.claude/skills/impeccable/scripts/live-poll.mjs:17
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 — sportivi-dashboard/.claude/skills/impeccable/scripts/modern-screenshot.umd.js:7
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 — sportivi-dashboard/src/services/aliexpressService.js:24
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 — sportivi-dashboard/src/services/githubVaultService.js:42
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 — sportivi-dashboard/src/services/sheetsService.js:30
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: sportivi-dashboard/.claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
sportivi-dashboard/.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: sportivi-dashboard/.claude/skills/impeccable/reference/teach.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.
sportivi-dashboard/.claude/skills/impeccable/reference/teach.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: sportivi-dashboard/.claude/skills/impeccable/scripts/command-metadata.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
sportivi-dashboard/.claude/skills/impeccable/scripts/command-metadata.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph 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/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:267
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:267 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:489
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard.html:489 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in jarvis.html:1614
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
jarvis.html:1614 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:420
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:420 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sportivi.html:492
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sportivi.html:492 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sportivi_v2.html:1139
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sportivi_v2.html:1139 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in voice.html:270
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
voice.html:270 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:1846
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:1846 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in sportivi-dashboard/.claude/skills/impeccable/scripts/modern-screenshot.umd.js:7
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/modern-screenshot.umd.js:7 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in sportivi-dashboard/.claude/skills/impeccable/scripts/is-generated.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/is-generated.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in sportivi-dashboard/.claude/skills/impeccable/scripts/live-poll.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live-poll.mjs:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live-server.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in sportivi-dashboard/.claude/skills/impeccable/scripts/live.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
sportivi-dashboard/.claude/skills/impeccable/scripts/live.mjs:20 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 12 placeholder/mock markers across 5 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 Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 57 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 24 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AE_APP_KEY`, `AE_APP_SECRET`, `AFFILIATE_TRIGGER_KEY`, `AFFILIATE_WF_ID`, `ANTHROPIC_API_KEY`, `ANTHROPIC_MODEL`, `BITLY_TOKEN`, `GARVIS_BASE_URL` + 16 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 102 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/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 44, 47, 71, 74, 80
.github/workflows/deploy.yml:44, 47, 71, 74, 80 (5 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — sportivi-dashboard/src/components/VoicePanelFloat.jsx:314
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 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 `contextLegacy` in sportivi-dashboard/.claude/skills/impeccable/scripts/impeccable-paths.mjs:20
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 `sportivi_v2` in app.py:1543
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 `withoutOld` in sportivi-dashboard/.claude/skills/impeccable/scripts/live-inject.mjs:118
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 Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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 — sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js:156
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 — sportivi-dashboard/src/services/githubVaultService.js:399
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 /
`app.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 /<path:filename>
`app.py` declares `ANY /<path: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: ANY /ae-analytics
`app.py` declares `ANY /ae-analytics` 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 /ae-proxy
`app.py` declares `ANY /ae-proxy` 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 /ae-status
`app.py` declares `ANY /ae-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /agent-logs
`app.py` declares `ANY /agent-logs` 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 /ai-routing-log
`app.py` declares `ANY /ai-routing-log` 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 /api/jarvis/chat
`app.py` declares `ANY /api/jarvis/chat` 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 /api/vault/daily-summary
`app.py` declares `ANY /api/vault/daily-summary` 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 /click-summary
`app.py` declares `ANY /click-summary` 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 /clicks-by-keyword
`app.py` declares `ANY /clicks-by-keyword` 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 /clicks-by-product
`app.py` declares `ANY /clicks-by-product` 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 /command
`app.py` declares `ANY /command` 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 /command-center
`app.py` declares `ANY /command-center` 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 /command-stream
`app.py` declares `ANY /command-stream` 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 /dashboard
`app.py` declares `ANY /dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /dashboard-old
`app.py` declares `ANY /dashboard-old` 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 /jarvis
`app.py` declares `ANY /jarvis` 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 /keyword-intelligence
`app.py` declares `ANY /keyword-intelligence` 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 /link-health
`app.py` declares `ANY /link-health` 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 /link-register
`app.py` declares `ANY /link-register` 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 /opportunity-feed
`app.py` declares `ANY /opportunity-feed` 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 /pipeline-health
`app.py` declares `ANY /pipeline-health` 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 /r/<tracking_id>
`app.py` declares `ANY /r/<tracking_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: ANY /research-status
`app.py` declares `ANY /research-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /runtime-metrics
`app.py` declares `ANY /runtime-metrics` 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 /runtime-queue
`app.py` declares `ANY /runtime-queue` 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 /runtime-status
`app.py` declares `ANY /runtime-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /scheduled-agents-health
`app.py` declares `ANY /scheduled-agents-health` 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 /sportivi
`app.py` declares `ANY /sportivi` 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 /sportivi-status
`app.py` declares `ANY /sportivi-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /system-status
`app.py` declares `ANY /system-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /telegram-members
`app.py` declares `ANY /telegram-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 /telegram-stats
`app.py` declares `ANY /telegram-stats` 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 /trend-intelligence
`app.py` declares `ANY /trend-intelligence` 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 /trend-scan
`app.py` declares `ANY /trend-scan` 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 /trigger-affiliate
`app.py` declares `ANY /trigger-affiliate` 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 /vault-proxy
`app.py` declares `ANY /vault-proxy` 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 /voice
`app.py` declares `ANY /voice` 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 /voice-transcribe
`app.py` declares `ANY /voice-transcribe` 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 /voice-tts
`app.py` declares `ANY /voice-tts` 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 /watchdog-status
`app.py` declares `ANY /watchdog-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: app.py (4223 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sportivi-dashboard/.claude/skills/impeccable/scripts/live-browser.js (4860 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/b1017b1e-9df5-44cb-919d-b9171d5ab8d1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b1017b1e-9df5-44cb-919d-b9171d5ab8d1/

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.