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

communist-prometheus/admin-website

https://github.com/communist-prometheus/admin-website · scanned 2026-06-17 01:50 UTC (1 month, 1 week ago)

145 raw signals (0 security + 145 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -22.0 (diff) · 145 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
54.7
/100
Security checks
55
0 findings
System graph
55
88.9% cov · 145 findings
Critical
3
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 3 High 20 Medium 84 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 145 Crowd 0 Layer: Frontend 7 Security 31 Cicd 1 Quality 69 Api 37
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 54.7/100 with 88.9% coverage. It contains 3845 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 145 findings — concentrated in quality (69), api (37), security (31). Risk profile is high: 3 critical, 20 high, 84 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 132 of 145 actionable findings. 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 src/sw/git/remote/build-auth-opts.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/sw/git/remote/build-auth-opts.ts:18
critical System graph security Secrets conf 1.00 Possible secret in src/sw/git/sync/clone/clone-options.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/sw/git/sync/clone/clone-options.ts:24
critical System graph security Secrets conf 1.00 Possible secret in src/sw/git/sync/pull/pull-repo.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/sw/git/sync/pull/pull-repo.ts:30
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.github.com/repos/${owner}/${repo}/contents/${path} (e2e-prod/prod-bundle-smoke.pw.ts:33)
`e2e-prod/prod-bundle-smoke.pw.ts:33` calls `DELETE https://api.github.com/repos/${owner}/${repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>/contents/<p>` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${cleanupPath} (e2e-prod/prod-manual-verify.pw.ts:255)
`e2e-prod/prod-manual-verify.pw.ts:255` calls `DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${cleanupPath}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.githu…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${path} (e2e-prod/repro-lang-switch-metadata.pw.ts:158)
`e2e-prod/repro-lang-switch-metadata.pw.ts:158` calls `DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.gith…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${path} (e2e-prod/repro-save-create.pw.ts:85)
`e2e-prod/repro-save-create.pw.ts:85` calls `DELETE https://api.github.com/repos/communist-prometheus/public-website-content/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/rep…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/cors/evil.example/x (src/api/cors-proxy.test.ts:50)
`src/api/cors-proxy.test.ts:50` calls `GET /api/cors/evil.example/x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/cors/evil.example/x` 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 /api/cors/github.com/owner/repo/contents/secrets (src/api/cors-proxy.test.ts:58)
`src/api/cors-proxy.test.ts:58` calls `GET /api/cors/github.com/owner/repo/contents/secrets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/cors/github.com/owner/repo/contents/secrets` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/github/content/blog (e2e-prod/prod-bundle-smoke.pw.ts:91)
`e2e-prod/prod-bundle-smoke.pw.ts:91` calls `GET /api/github/content/blog` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/github/content/blog` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/github/content/blog (e2e-prod/prod-manual-verify.pw.ts:60)
`e2e-prod/prod-manual-verify.pw.ts:60` calls `GET /api/github/content/blog` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/github/content/blog` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/github/file?path=${encodeURIComponent(p)} (e2e/content/create-edit-roundtrip.spec.ts:23)
`e2e/content/create-edit-roundtrip.spec.ts:23` calls `GET /api/github/file?path=${encodeURIComponent(p)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/github/file` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${owner}/${repo}/contents/${path} (e2e-prod/integration-create.pw.ts:19)
`e2e-prod/integration-create.pw.ts:19` calls `GET https://api.github.com/repos/${owner}/${repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>/contents/<p>` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${owner}/${repo}/contents/${path}?ref=${branch} (e2e-prod/prod-bundle-smoke.pw.ts:27)
`e2e-prod/prod-bundle-smoke.pw.ts:27` calls `GET https://api.github.com/repos/${owner}/${repo}/contents/${path}?ref=${branch}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>/conte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/communist-prometheus/public-website-content/contents/${cleanupPath}?ref=master (e2e-prod/prod-manual-verify.pw.ts:249)
`e2e-prod/prod-manual-verify.pw.ts:249` calls `GET https://api.github.com/repos/communist-prometheus/public-website-content/contents/${cleanupPath}?ref=master` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/communist-prometheus/public-website-content/contents/blog/${SLUG}/index.en.md?ref=master (e2e-prod/prod-manual-verify.pw.ts:179)
`e2e-prod/prod-manual-verify.pw.ts:179` calls `GET https://api.github.com/repos/communist-prometheus/public-website-content/contents/blog/${SLUG}/index.en.md?ref=master` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: HEAD /sw.js (src/composables/useSWBridge/check-sw-available.ts:18)
`src/composables/useSWBridge/check-sw-available.ts:18` calls `HEAD /sw.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sw.js` 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 /api/github/file (e2e-prod/prod-bundle-smoke.pw.ts:118)
`e2e-prod/prod-bundle-smoke.pw.ts:118` calls `POST /api/github/file` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/github/file` 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 /api/oauth/token (src/api/token-handler.test.ts:20)
`src/api/token-handler.test.ts:20` calls `POST /api/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/oauth/token` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/sw/init (src/composables/useSWBridge/try-fetch-init.ts:10)
`src/composables/useSWBridge/try-fetch-init.ts:10` calls `POST /api/sw/init` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sw/init` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/github/file/stage (e2e-realmode/schema-gate.spec.ts:30)
`e2e-realmode/schema-gate.spec.ts:30` calls `PUT /api/github/file/stage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/github/file/stage` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/sw/handlers/route.ts:43
Found a known-risky pattern (exec_used). Review and replace if possible.
src/sw/handlers/route.ts:43 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/views/ContentView/run-optimistic-delete.ts:58
Found a known-risky pattern (exec_used). Review and replace if possible.
src/views/ContentView/run-optimistic-delete.ts:58 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — e2e-prod/integration-create.pw.ts:19
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 — e2e-prod/prod-bundle-smoke.pw.ts:27
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 — e2e-prod/prod-manual-verify.pw.ts:60
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 — e2e-prod/repro-lang-switch-metadata.pw.ts:153
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 — e2e-prod/repro-save-create.pw.ts:80
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 — e2e-realmode/astro-schema-drift.spec.ts:66
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 — e2e-realmode/helpers/astro-validate.ts: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 — e2e-realmode/helpers/sandbox-config.ts:13
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 — e2e-realmode/helpers/sandbox-read.ts:19
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 — e2e-realmode/schema-gate.spec.ts: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — e2e/content/create-edit-roundtrip.spec.ts:23
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 — scripts/deploy-status.ts:35
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 — scripts/migrate-labels.ts: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 — scripts/sandbox-config.ts:37
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 — scripts/sandbox-gh.ts:19
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 — services/auth-worker/src/session-handler.test.ts:69
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 — services/comms-worker/src/dispatch/force-route.test.ts:54
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 — services/comms-worker/src/dispatch/full-flow.test.ts:80
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 — services/comms-worker/src/health.test.ts:11
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 — services/comms-worker/src/middleware/require-session.test.ts:48
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 — services/comms-worker/src/schedule/routes.test.ts:55
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 — services/comms-worker/src/send-log/route.test.ts:71
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 — services/comms-worker/src/subscribers/routes.test.ts:57
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 — services/comms-worker/src/unsubscribe/routes.test.ts: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 — services/comms-worker/src/webhooks/routes.test.ts:53
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 — services/log-collector/src/auth-middleware.test.ts:25
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 — services/log-collector/src/batch-size-guard.test.ts:14
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 — services/log-collector/src/gh-user.ts:22
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 — services/log-collector/src/health.test.ts:11
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 — services/log-collector/src/otlp-handlers.test.ts:36
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 — services/log-collector/src/rate-limit.test.ts: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 — src/api/cors-proxy.ts:31
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/api/token-handler.ts:14
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/composables/useAuth/exchange-token.ts:40
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/composables/useAuth/fetch-github-user.ts:11
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/composables/useAuth/mint-session.ts:38
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/composables/useDeployStatus/gh-fetch.ts:13
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/composables/useDeployStatus/job-logs.ts:48
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/composables/useSWBridge/check-sw-available.ts:18
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/composables/useSWBridge/sw-fetch.ts:45
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/features/tickets/api/add-comment.ts:26
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/features/tickets/api/gh-tickets.ts:41
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/features/tickets/api/put-blob/http.ts:50
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/features/tickets/api/put-content.ts:34
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/features/tickets/api/ticket-actions.ts:26
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/features/tickets/api/ticket-state.ts:22
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/stores/comms-http.ts:21
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/sw/rbac/github-api.ts:25
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/sw/rbac/handle-revoke-invite.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 — src/sw/rbac/invite-post.ts:11
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/sw/rbac/org-role-membership.ts:21
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/sw/rbac/team-membership-ops.ts:21
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 — vite/proxy-helpers.ts:54
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 — worker.ts:15
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: .claude/settings.local.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.
.claude/settings.local.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. 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 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 services/comms-worker/src/app.ts:35
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/comms-worker/src/app.ts:35 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in e2e/comms-walkthrough/overlay.ts:80
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
e2e/comms-walkthrough/overlay.ts:80 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/directives/render.ts:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/directives/render.ts:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/features/newspaper/html-to-fb2/html-to-fb2.ts:14
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/features/newspaper/html-to-fb2/html-to-fb2.ts:14 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/probe-pdf-upload.pw.ts:76
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/probe-pdf-upload.pw.ts:76 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/prod-bundle-smoke.pw.ts:80
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/prod-bundle-smoke.pw.ts:80 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/prod-manual-verify.pw.ts:53
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/prod-manual-verify.pw.ts:53 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/repro-lang-switch-metadata.pw.ts:47
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/repro-lang-switch-metadata.pw.ts:47 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/repro-save-broken.pw.ts:83
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/repro-save-broken.pw.ts:83 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/repro-save-create.pw.ts:113
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/repro-save-create.pw.ts:113 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/repro-slug-alt.pw.ts:25
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/repro-slug-alt.pw.ts:25 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/upload-newspaper.pw.ts:68
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/upload-newspaper.pw.ts:68 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-prod/verify-edit-flow.pw.ts:71
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-prod/verify-edit-flow.pw.ts:71 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e-realmode/helpers/seed-token.ts:21
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e-realmode/helpers/seed-token.ts:21 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e/auth/helpers.ts:10
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e/auth/helpers.ts:10 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e/auth/setup.ts:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e/auth/setup.ts:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev-token.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dev-token.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/kill-port.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/kill-port.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in vite.config.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
vite.config.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/components/MarkdownEditor/MarkdownPreview.vue:36
Found a known-risky pattern (vue_v_html). Review and replace if possible.
src/components/MarkdownEditor/MarkdownPreview.vue:36 Vue v html
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 100 placeholder/mock markers across 44 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 quality Integrity conf 1.00 15 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BASE_URL`, `BROWSERS`, `CI`, `DEV`, `GITHUB_OWNER`, `GITHUB_REPO`, `PROBE_BASE_URL`, `VITE_AUTH_BASE` + 7 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 16 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/components/CreateContentDialog/CreateContentDialog.vue:57
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/components/LinksEditor/LinkRow.vue:49
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 Tests conf 1.00 Low test-to-source ratio
196 tests / 1050 src (ratio 0.19).
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 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/deploy-status.ts:50
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 — scripts/migrate-labels.ts:50
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 — scripts/migrate-mocks.ts:41
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 — scripts/verify-sw-browser-safe.ts:46
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 — services/comms-worker/src/log/structured.ts: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: DELETE /api/subscribers/:id
`services/comms-worker/src/subscribers/routes.ts` declares `DELETE /api/subscribers/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cutoff
`services/comms-worker/src/schedule/routes.ts` declares `GET /api/cutoff` 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/runs
`services/comms-worker/src/send-log/route.ts` declares `GET /api/runs` 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/schedule
`services/comms-worker/src/schedule/routes.ts` declares `GET /api/schedule` 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/subscribers
`services/comms-worker/src/subscribers/routes.ts` declares `GET /api/subscribers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /unsubscribe
`services/comms-worker/src/unsubscribe/routes.ts` declares `GET /unsubscribe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/subscribers/:id
`services/comms-worker/src/subscribers/routes.ts` declares `PATCH /api/subscribers/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/dispatch
`services/comms-worker/src/dispatch/force-route.ts` declares `POST /api/dispatch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/subscribers
`services/comms-worker/src/subscribers/routes.ts` declares `POST /api/subscribers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/logout
`services/auth-worker/src/logout-handler.ts` declares `POST /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 /auth/session
`services/auth-worker/src/session-handler.ts` declares `POST /auth/session` 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 /unsubscribe
`services/comms-worker/src/unsubscribe/routes.ts` declares `POST /unsubscribe` 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/logs
`services/log-collector/src/otlp-handlers.ts` declares `POST /v1/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: POST /v1/traces
`services/log-collector/src/otlp-handlers.ts` declares `POST /v1/traces` 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 /webhooks/resend
`services/comms-worker/src/webhooks/routes.ts` declares `POST /webhooks/resend` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/cutoff
`services/comms-worker/src/schedule/routes.ts` declares `PUT /api/cutoff` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/schedule
`services/comms-worker/src/schedule/routes.ts` declares `PUT /api/schedule` 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 /api/*
`services/comms-worker/src/app.ts` declares `USE /api/*` 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/*
`services/log-collector/src/index.ts` 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
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/30cf4fff-71f3-4d1e-b36b-c77caddff4e1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/30cf4fff-71f3-4d1e-b36b-c77caddff4e1/

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.