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

SilentGTX/Blissful

https://github.com/SilentGTX/Blissful · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

404 raw signals (0 security + 404 graph)

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

Complete repo analysis

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

JSON
Combined
51.0
/100
Security checks
51
0 findings
System graph
51
100.0% cov · 385 findings
Critical
1
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 1 High 29 Medium 55 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 385 Crowd 0 Layer: Software 5 Frontend 34 Hardware 1 Security 23 Cicd 4 Quality 263 Api 55
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 51.0/100 with 100.0% coverage. It contains 2792 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 404 findings — concentrated in quality (278), api (55), frontend (34). Risk profile is high: 1 critical, 29 high, 72 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in apps/desktop-blissful/installer/README.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/desktop-blissful/installer/README.md:41
high System graph api Wiring conf 1.00 Dangling fetch: GET /addon-proxy?url=${encodeURIComponent(url)} (apps/web-blissful/src/lib/tmdb.ts:44)
`apps/web-blissful/src/lib/tmdb.ts:44` calls `GET /addon-proxy?url=${encodeURIComponent(url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/addon-proxy` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /imdb-rating?imdbId=${encodeURIComponent(imdbId)} (apps/web-blissful/src/lib/useImdbRating.ts:36)
`apps/web-blissful/src/lib/useImdbRating.ts:36` calls `GET /imdb-rating?imdbId=${encodeURIComponent(imdbId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/imdb-rating` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /opensubs?${osQs.toString()} (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:2004)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:2004` calls `GET /opensubs?${osQs.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/opensubs` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /probe-streams?url=${encodeURIComponent(c.stream.url)} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:1175)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:1175` calls `GET /probe-streams?url=${encodeURIComponent(c.stream.url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/probe-streams` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /probe-streams?url=${encodeURIComponent(probeTarget)} (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:2113)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:2113` calls `GET /probe-streams?url=${encodeURIComponent(probeTarget)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/probe-streams` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /rd-by-hash?${qs.toString()} (apps/web-blissful/src/lib/watchPartySource.ts:169)
`apps/web-blissful/src/lib/watchPartySource.ts:169` calls `GET /rd-by-hash?${qs.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/rd-by-hash` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /rd-by-hash?infoHash=${encodeURIComponent(ih)} (apps/web-blissful/src/components/BananasPicker.tsx:229)
`apps/web-blissful/src/components/BananasPicker.tsx:229` calls `GET /rd-by-hash?infoHash=${encodeURIComponent(ih)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/rd-by-hash` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /rd-fallback?type=${type}&id=${encodeURIComponent(id)} (apps/web-blissful/src/lib/fallbackReleases.ts:111)
`apps/web-blissful/src/lib/fallbackReleases.ts:111` calls `GET /rd-fallback?type=${type}&id=${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/rd-fallback` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /rd-fallback?type=${type}&id=${encodeURIComponent(streamId)} (apps/web-blissful/src/pages/PlayerPage.tsx:271)
`apps/web-blissful/src/pages/PlayerPage.tsx:271` calls `GET /rd-fallback?type=${type}&id=${encodeURIComponent(streamId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/rd-fallback` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /rd-fallback?type=${type}&id=${encodeURIComponent(streamId)} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:1032)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:1032` calls `GET /rd-fallback?type=${type}&id=${encodeURIComponent(streamId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/rd-fallback` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /resolve-url?url=${encodeURIComponent(cand.stream.url)} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:1207)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:1207` calls `GET /resolve-url?url=${encodeURIComponent(cand.stream.url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/resolve-url` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /resolve-url?url=${encodeURIComponent(props.url)} (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1612)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1612` calls `GET /resolve-url?url=${encodeURIComponent(props.url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/resolve-url` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /resolve-url?url=${encodeURIComponent(s.url)} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:92)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:92` calls `GET /resolve-url?url=${encodeURIComponent(s.url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/resolve-url` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /skip-times?${params.toString()} (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1686)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1686` calls `GET /skip-times?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skip-times` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /stremio/login-fb-get-acc/${state} (apps/web-blissful/src/lib/stremioFacebook.ts:50)
`apps/web-blissful/src/lib/stremioFacebook.ts:50` calls `GET /stremio/login-fb-get-acc/${state}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stremio/login-fb-get-acc/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /tmdb-episode-rating?${params.toString()} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:656)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:656` calls `GET /tmdb-episode-rating?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tmdb-episode-rating` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /tmdb-find?imdbId=${encodeURIComponent(imdbId)} (apps/web-blissful/src/lib/tmdb.ts:58)
`apps/web-blissful/src/lib/tmdb.ts:58` calls `GET /tmdb-find?imdbId=${encodeURIComponent(imdbId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tmdb-find` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /tmdb-season-info?tmdbId=${props.tmdbId}&season=${season} (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1431)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1431` calls `GET /tmdb-season-info?tmdbId=${props.tmdbId}&season=${season}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tmdb-season-info` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /tmdb-season-info?tmdbId=${tid}&season=${n} (apps/web-blissful/src/pages/DetailPage.tsx:396)
`apps/web-blissful/src/pages/DetailPage.tsx:396` calls `GET /tmdb-season-info?tmdbId=${tid}&season=${n}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tmdb-season-info` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /transcode-audio?url=${encodeURIComponent(transcodeAudioSrc)} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:918)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:918` calls `GET /transcode-audio?url=${encodeURIComponent(transcodeAudioSrc)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/transcode-audio` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /videasy-sources?${params.toString()} (apps/web-blissful/src/pages/PlayerPageWeb.tsx:774)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:774` calls `GET /videasy-sources?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/videasy-sources` 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.ani.zip/mappings?${param}=${encodeURIComponent(value)} (apps/web-blissful/src/lib/aniskip.ts:69)
`apps/web-blissful/src/lib/aniskip.ts:69` calls `GET https://api.ani.zip/mappings?${param}=${encodeURIComponent(value)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.ani.zip/mappings` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.themoviedb.org/3/find/${imdbId}?api_key=${encodeURIComponent(key)}&external_source=imdb_id (apps/android-blissful/src/lib/tmdbArt.ts:79)
`apps/android-blissful/src/lib/tmdbArt.ts:79` calls `GET https://api.themoviedb.org/3/find/${imdbId}?api_key=${encodeURIComponent(key)}&external_source=imdb_id` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://torrentio.strem.fun/stream/movie/${imdbId}.json (scripts/e2e/watchparty-v2.mjs:385)
`scripts/e2e/watchparty-v2.mjs:385` calls `GET https://torrentio.strem.fun/stream/movie/${imdbId}.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/torrentio.strem.fun/stream/movie/<p>.json` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /player-log (apps/web-blissful/src/components/BlissfulPlayer/index.tsx:3076)
`apps/web-blissful/src/components/BlissfulPlayer/index.tsx:3076` calls `POST /player-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/player-log` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /player-log (apps/web-blissful/src/lib/playerEnv.ts:115)
`apps/web-blissful/src/lib/playerEnv.ts:115` calls `POST /player-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/player-log` 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 /player-log (apps/web-blissful/src/pages/PlayerPageWeb.tsx:284)
`apps/web-blissful/src/pages/PlayerPageWeb.tsx:284` calls `POST /player-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/player-log` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /storage/watch-party (scripts/e2e/watchparty.mjs:397)
`scripts/e2e/watchparty.mjs:397` calls `POST /storage/watch-party` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/storage/watch-party` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in apps/shared/addon-proxy/videasy-decrypt.js:72
Found a known-risky pattern (new_function_used). Review and replace if possible.
apps/shared/addon-proxy/videasy-decrypt.js:72 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/android-blissful/src/lib/addons.ts:56
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 — apps/android-blissful/src/lib/useImdbRating.ts:43
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 — apps/android-blissful/src/lib/watchParty.ts:150
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 — apps/shared/addon-proxy/server.js:1114
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 — apps/shared/blissful-core/src/adapters.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/shared/blissful-core/src/blissfulStorageApi.ts:28
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 — apps/shared/blissful-core/src/stremioAddon.ts:208
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 — apps/shared/blissful-storage/server.js:1364
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 — apps/web-blissful/src/components/BlissfulPlayer/index.tsx:1431
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 — apps/web-blissful/src/components/NativeMpvPlayer.tsx:843
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 — apps/web-blissful/src/components/Rating.tsx: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 — apps/web-blissful/src/features/home/hooks/useAddonRows.ts:44
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 — apps/web-blissful/src/lib/fallbackReleases.ts:111
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 — apps/web-blissful/src/lib/introdb.ts:64
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 — apps/web-blissful/src/lib/storageApi.ts:51
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 — apps/web-blissful/src/lib/stremioAddon.ts:246
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 — apps/web-blissful/src/lib/stremioFacebook.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 — apps/web-blissful/src/lib/subtitleUtils.ts:52
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 — apps/web-blissful/src/lib/tmdb.ts:44
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 — apps/web-blissful/src/lib/watchParty.ts:442
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 — apps/web-blissful/src/pages/PlayerPageWeb.tsx:92
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 — apps/web-blissful/vite.config.ts:187
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/suites/social-ws.protocol.spec.ts:199
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/suites/watch-party.guest-controls.web.spec.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 — e2e/suites/watch-party.sync.desktop.spec.ts:20
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/e2e/watchparty-v2.mjs:332
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/e2e/watchparty.mjs:397
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 quality Integrity conf 1.00 16 occurrences Frontend route `/player-spike` has no Link/navigate to it — apps/web-blissful/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
16 occurrences
repo-level (16 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 103, 108, 266
.github/workflows/release.yml:103, 108, 266 (3 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/shared/addon-proxy/server.js:720
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/shared/addon-proxy/server.js:720 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in infra/scripts/blissful-transcoder.py:248
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
infra/scripts/blissful-transcoder.py:248 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in scripts/e2e/watchparty.mjs:203
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
scripts/e2e/watchparty.mjs:203 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/dev-launcher/renderer/renderer.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
scripts/dev-launcher/renderer/renderer.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/shared/addon-proxy/server.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/shared/addon-proxy/server.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in e2e/run.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
e2e/run.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev-android.cjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dev-android.cjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev-launcher/lib/manager.cjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dev-launcher/lib/manager.cjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev.cjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dev.cjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/episode-change-share.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/episode-change-share.mjs:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/host-relay.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/host-relay.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/relay-crash-repro.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/relay-crash-repro.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/verify-leftover-replace.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/verify-leftover-replace.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/verify-renderer-recovery.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/verify-renderer-recovery.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/verify-software-transcode.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/verify-software-transcode.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/watchparty-v2.mjs:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/watchparty-v2.mjs:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e/watchparty.mjs:29
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e/watchparty.mjs:29 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-cargo.cjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-cargo.cjs:11 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 165 placeholder/mock markers across 55 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
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
9 test file(s) for 445 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 122 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 3 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 89, 113, 234
.github/workflows/release.yml:89, 113, 234 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web-blissful/src/features/home/components/ModernHeroPanel.tsx:100
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `failed_infringement_v2` in apps/web-blissful/src/pages/PlayerPageWeb.tsx:70
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 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.
apps/android-blissful/package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/scripts/blissful-transcoder.py:166
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/scripts/videasy-resolver.py:316
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/scripts/blissful-transcoder.py:163
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/scripts/videasy-resolver.py:305
low System graph software Dead code conf 1.00 Possibly dead Python function: prune_cache_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/scripts/blissful-transcoder.py:85
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 — apps/android-blissful/scripts/link-core.js:32
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 — apps/shared/addon-proxy/server.js:962
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 — apps/shared/blissful-storage/server.js:322
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 — apps/web-blissful/src/layout/app-shell/hooks/useStoredStateSync.ts:63
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/dev-launcher/main.js:35
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 /friends/:id
`apps/shared/blissful-storage/server.js` declares `DELETE /friends/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /library/:id
`apps/shared/blissful-storage/server.js` declares `DELETE /library/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dms/:userId
`apps/shared/blissful-storage/server.js` declares `GET /dms/:userId` 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 /dms/search
`apps/shared/blissful-storage/server.js` declares `GET /dms/search` 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 /friends
`apps/shared/blissful-storage/server.js` declares `GET /friends` 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 /home
`apps/shared/blissful-storage/server.js` declares `GET /home` 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 /settings
`apps/shared/blissful-storage/server.js` declares `GET /settings` 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 /state
`apps/shared/blissful-storage/server.js` declares `GET /state` 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 /stremio/status
`apps/shared/blissful-storage/server.js` declares `GET /stremio/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: GET /users/search
`apps/shared/blissful-storage/server.js` declares `GET /users/search` 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 /watch-party/:code
`apps/shared/blissful-storage/server.js` declares `GET /watch-party/:code` 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 /friends/:id/nickname
`apps/shared/blissful-storage/server.js` declares `PATCH /friends/:id/nickname` 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 /dms/:userId
`apps/shared/blissful-storage/server.js` declares `POST /dms/:userId` 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 /friends/:id/accept
`apps/shared/blissful-storage/server.js` declares `POST /friends/:id/accept` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /friends/request
`apps/shared/blissful-storage/server.js` declares `POST /friends/request` 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 /home
`apps/shared/blissful-storage/server.js` declares `POST /home` 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 /library/import
`apps/shared/blissful-storage/server.js` declares `POST /library/import` 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 /settings
`apps/shared/blissful-storage/server.js` declares `POST /settings` 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 /state
`apps/shared/blissful-storage/server.js` declares `POST /state` 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 /stremio/link-token
`apps/shared/blissful-storage/server.js` declares `POST /stremio/link-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 /stremio/sync
`apps/shared/blissful-storage/server.js` declares `POST /stremio/sync` 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 /stremio/sync-item
`apps/shared/blissful-storage/server.js` declares `POST /stremio/sync-item` 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 /stremio/unlink
`apps/shared/blissful-storage/server.js` declares `POST /stremio/unlink` 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 /watch-party
`apps/shared/blissful-storage/server.js` declares `POST /watch-party` 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 /watch-party/:code/verify
`apps/shared/blissful-storage/server.js` declares `POST /watch-party/:code/verify` 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: PUT /library/:id
`apps/shared/blissful-storage/server.js` declares `PUT /library/: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: USE /addon-proxy
`apps/web-blissful/vite.config.ts` declares `USE /addon-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 quality Complexity conf 1.00 Very large file: apps/android-blissful/src/screens/PlayerScreen.tsx (1083 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/shared/addon-proxy/server.js (2592 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/shared/blissful-storage/server.js (3002 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web-blissful/src/components/BlissfulPlayer/index.tsx (4041 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web-blissful/src/components/NativeMpvPlayer.tsx (3643 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web-blissful/src/pages/PlayerPageWeb.tsx (1561 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/90c7f337-b0d1-4cee-a5eb-6baea9f9e961/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/90c7f337-b0d1-4cee-a5eb-6baea9f9e961/

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.