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

TsinHzl/agy-cc-proxy

https://github.com/TsinHzl/agy-cc-proxy · scanned 2026-06-16 00:42 UTC (2 months, 1 week ago)

99 raw signals (0 security + 99 graph)

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

Complete repo analysis

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

JSON
Combined
60.1
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 77 findings
Critical
6
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 6 High 29 Medium 11 Low 23 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 77 Crowd 0 Layer: Frontend 7 Security 11 Cicd 2 Quality 15 Api 42
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.1/100 with 100.0% coverage. It contains 709 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 99 findings — concentrated in api (42), security (32), quality (15). Risk profile is high: 27 critical, 29 high, 11 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 69 of 77 actionable findings. 99 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 6 occurrences Possible secret in public/js/translations/en.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 236, 292, 294, 295, 296, 377
public/js/translations/en.js:236, 292, 294, 295, 296, 377 (6 hits)
critical System graph security Secrets conf 1.00 6 occurrences Possible secret in public/js/translations/id.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 268, 327, 329, 330, 331, 420
public/js/translations/id.js:268, 327, 329, 330, 331, 420 (6 hits)
critical System graph security Secrets conf 1.00 5 occurrences Possible secret in public/js/translations/pt.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 215, 270, 272, 273, 274
public/js/translations/pt.js:215, 270, 272, 273, 274 (5 hits)
critical System graph security Secrets conf 1.00 6 occurrences Possible secret in public/js/translations/tr.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 218, 274, 276, 277, 278, 363
public/js/translations/tr.js:218, 274, 276, 277, 278, 363 (6 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in public/js/translations/zh.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 236, 292, 381
public/js/translations/zh.js:236, 292, 381 (3 hits)
critical System graph security Secrets conf 1.00 Possible secret in src/config.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/config.js:189
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/claude/presets/__test_preset__ (tests/frontend/test-frontend-settings.cjs:375)
`tests/frontend/test-frontend-settings.cjs:375` calls `DELETE /api/claude/presets/__test_preset__` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/claude/presets/__test_preset__` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /${comp} (tests/frontend/test-frontend-settings.cjs:269)
`tests/frontend/test-frontend-settings.cjs:269` calls `GET /${comp}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /${store} (tests/frontend/test-frontend-settings.cjs:292)
`tests/frontend/test-frontend-settings.cjs:292` calls `GET /${store}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /app.js (tests/frontend/test-frontend-settings.cjs:304)
`tests/frontend/test-frontend-settings.cjs:304` calls `GET /app.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/app.js` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /index.html (tests/frontend/test-frontend-accounts.cjs:137)
`tests/frontend/test-frontend-accounts.cjs:137` calls `GET /index.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/index.html` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /index.html (tests/frontend/test-frontend-accounts.cjs:148)
`tests/frontend/test-frontend-accounts.cjs:148` calls `GET /index.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/index.html` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/${view}.html (tests/frontend/test-frontend-settings.cjs:248)
`tests/frontend/test-frontend-settings.cjs:248` calls `GET /views/${view}.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/<p>.html` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:105)
`tests/frontend/test-frontend-accounts.cjs:105` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:116)
`tests/frontend/test-frontend-accounts.cjs:116` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:126)
`tests/frontend/test-frontend-accounts.cjs:126` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:38)
`tests/frontend/test-frontend-accounts.cjs:38` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:68)
`tests/frontend/test-frontend-accounts.cjs:68` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:82)
`tests/frontend/test-frontend-accounts.cjs:82` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/accounts.html (tests/frontend/test-frontend-accounts.cjs:95)
`tests/frontend/test-frontend-accounts.cjs:95` calls `GET /views/accounts.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/accounts.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/dashboard.html (tests/frontend/test-frontend-dashboard.cjs:112)
`tests/frontend/test-frontend-dashboard.cjs:112` calls `GET /views/dashboard.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/dashboard.html` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/dashboard.html (tests/frontend/test-frontend-dashboard.cjs:37)
`tests/frontend/test-frontend-dashboard.cjs:37` calls `GET /views/dashboard.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/dashboard.html` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/dashboard.html (tests/frontend/test-frontend-dashboard.cjs:70)
`tests/frontend/test-frontend-dashboard.cjs:70` calls `GET /views/dashboard.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/dashboard.html` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/dashboard.html (tests/frontend/test-frontend-dashboard.cjs:91)
`tests/frontend/test-frontend-dashboard.cjs:91` calls `GET /views/dashboard.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/dashboard.html` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/logs.html (tests/frontend/test-frontend-logs.cjs:107)
`tests/frontend/test-frontend-logs.cjs:107` calls `GET /views/logs.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/logs.html` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/logs.html (tests/frontend/test-frontend-logs.cjs:120)
`tests/frontend/test-frontend-logs.cjs:120` calls `GET /views/logs.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/logs.html` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/logs.html (tests/frontend/test-frontend-logs.cjs:35)
`tests/frontend/test-frontend-logs.cjs:35` calls `GET /views/logs.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/logs.html` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/logs.html (tests/frontend/test-frontend-logs.cjs:84)
`tests/frontend/test-frontend-logs.cjs:84` calls `GET /views/logs.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/logs.html` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/logs.html (tests/frontend/test-frontend-logs.cjs:97)
`tests/frontend/test-frontend-logs.cjs:97` calls `GET /views/logs.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/logs.html` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/settings.html (tests/frontend/test-frontend-settings.cjs:39)
`tests/frontend/test-frontend-settings.cjs:39` calls `GET /views/settings.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/settings.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/settings.html (tests/frontend/test-frontend-settings.cjs:396)
`tests/frontend/test-frontend-settings.cjs:396` calls `GET /views/settings.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/settings.html` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/settings.html (tests/frontend/test-frontend-settings.cjs:49)
`tests/frontend/test-frontend-settings.cjs:49` calls `GET /views/settings.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/settings.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/settings.html (tests/frontend/test-frontend-settings.cjs:70)
`tests/frontend/test-frontend-settings.cjs:70` calls `GET /views/settings.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/settings.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /views/settings.html (tests/frontend/test-frontend-settings.cjs:93)
`tests/frontend/test-frontend-settings.cjs:93` calls `GET /views/settings.html` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/views/settings.html` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${ANTIGRAVITY_AUTH_PORT}/ (src/auth/token-extractor.js:25)
`src/auth/token-extractor.js:25` calls `GET http://127.0.0.1:${ANTIGRAVITY_AUTH_PORT}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/app.js:32
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 — public/js/utils.js:8
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 — src/utils/helpers.js:89
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in src/server.js:80
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/server.js:80 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:27
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/app.js:27 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/accounts.js:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/accounts.js:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/native-module-helper.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/native-module-helper.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/version-detector.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/version-detector.js:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 24 placeholder/mock markers across 9 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 Debug conf 1.00 Debug logging residue appears in source files
Found 71 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 2 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 12, 15
.github/workflows/publish.yml:12, 15 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
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 — public/js/utils/ui-logger.js:87
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli/accounts.js:106
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/utils/logger.js:72
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 — tests/test-version-detection.js:6
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: GET /api/claude/mode
`src/webui/index.js` declares `GET /api/claude/mode` 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 /api/logs/stream
`src/webui/index.js` declares `GET /api/logs/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: GET /api/stats/history
`src/modules/usage-stats.js` declares `GET /api/stats/history` 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 /v1/models
`src/server.js` declares `GET /v1/models` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`src/server.js` 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 /api/auth/login
`src/webui/index.js` declares `POST /api/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/logout
`src/webui/index.js` declares `POST /api/auth/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 /api/claude/mode
`src/webui/index.js` declares `POST /api/claude/mode` 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-token
`src/server.js` declares `POST /refresh-token` 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 /test/clear-signature-cache
`src/server.js` declares `POST /test/clear-signature-cache` 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 /v1/messages
`src/server.js` declares `POST /v1/messages` 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 /v1/messages/count_tokens
`src/server.js` declares `POST /v1/messages/count_tokens` 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: USE /v1
`src/server.js` declares `USE /v1` 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: public/js/components/server-config.js (1183 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/webui/index.js (1374 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/a9a4cf5d-5ee7-4905-bf60-3cb2d003599a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a9a4cf5d-5ee7-4905-bf60-3cb2d003599a/

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.