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

aquiloplays/loadout

https://github.com/aquiloplays/loadout · scanned 2026-06-17 01:35 UTC (1 month, 2 weeks ago)

655 raw signals (0 security + 655 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -11.9 (diff) · 632 actionable findings from 1 signal source. 23 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
64.8
/100
Security checks
65
0 findings
System graph
65
100.0% cov · 632 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 161 Medium 136 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 632 Crowd 0 Layer: Software 16 Frontend 4 Security 67 Cicd 4 Quality 383 Api 158
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 64.8/100 with 100.0% coverage. It contains 5972 nodes across 12 cross-layer flows, written primarily in mixed languages. Engine surfaced 655 findings — concentrated in quality (399), api (158), security (67). Risk profile is high: 0 critical, 161 high, 137 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${oldBanner.id} (discord-bot/worker.js:5392)
`discord-bot/worker.js:5392` calls `DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${oldBanner.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/ch…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${prior.id} (discord-bot/worker.js:4445)
`discord-bot/worker.js:4445` calls `DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${prior.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channe…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${stamp.messageId} (discord-bot/worker.js:4425)
`discord-bot/worker.js:4425` calls `DELETE https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages/${stamp.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${encodeURIComponent(chId)} (discord-bot/voice-temp.js:141)
`discord-bot/voice-temp.js:141` calls `DELETE https://discord.com/api/v10/channels/${encodeURIComponent(chId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${encodeURIComponent(prior.channelId)}/messages/${prior.messageId} (discord-bot/worker.js:4610)
`discord-bot/worker.js:4610` calls `DELETE https://discord.com/api/v10/channels/${encodeURIComponent(prior.channelId)}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${m.channelId}/messages/${m.messageId} (discord-bot/cn-games-list-hub.js:118)
`discord-bot/cn-games-list-hub.js:118` calls `DELETE https://discord.com/api/v10/channels/${m.channelId}/messages/${m.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/channel-hubs.js:181)
`discord-bot/channel-hubs.js:181` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/cn-vote-hub.js:69)
`discord-bot/cn-vote-hub.js:69` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/lfg-hub.js:122)
`discord-bot/lfg-hub.js:122` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/vote-hub.js:350)
`discord-bot/vote-hub.js:350` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/vote-hub.js:524)
`discord-bot/vote-hub.js:524` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId} (discord-bot/vote-hub.js:795)
`discord-bot/vote-hub.js:795` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${prior.channelId}/pins/${prior.messageId} (discord-bot/vote-hub.js:522)
`discord-bot/vote-hub.js:522` calls `DELETE https://discord.com/api/v10/channels/${prior.channelId}/pins/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/pin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${priorRaw.channelId}/messages/${priorRaw.messageId} (discord-bot/onboarding.js:787)
`discord-bot/onboarding.js:787` calls `DELETE https://discord.com/api/v10/channels/${priorRaw.channelId}/messages/${priorRaw.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/chan…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/channels/${rulesCh.id}/messages/${oldVerify.id} (discord-bot/worker.js:5919)
`discord-bot/worker.js:5919` calls `DELETE https://discord.com/api/v10/channels/${rulesCh.id}/messages/${oldVerify.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules/${r.id} (discord-bot/worker.js:6598)
`discord-bot/worker.js:6598` calls `DELETE https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules/${r.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/auto-moder…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.epicgames.dev/epic/oauth/v2/userInfo (discord-bot/progression/oauth/epic.js:13)
`discord-bot/progression/oauth/epic.js:13` calls `GET https://api.epicgames.dev/epic/oauth/v2/userInfo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.epicgames.dev/epic/oauth/v2/userinfo` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=${env.STEAM_API_KEY}&steamids=${steamId64} (discord-bot/progression/oauth/steam.js:80)
`discord-bot/progression/oauth/steam.js:80` calls `GET https://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=${env.STEAM_API_KEY}&steamids=${steamId64}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.twitch.tv/helix/users (discord-bot/punchcard.js:459)
`discord-bot/punchcard.js:459` calls `GET https://api.twitch.tv/helix/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twitch.tv/helix/users` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://aquilo.gg/api/community/supporter-wall (aquilo-gg/overlays/starting-soon/main.js:502)
`aquilo-gg/overlays/starting-soon/main.js:502` calls `GET https://aquilo.gg/api/community/supporter-wall` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/aquilo.gg/api/community/supporter-wall` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://aquilo.gg/api/schedule (aquilo-gg/overlays/starting-soon/main.js:87)
`aquilo-gg/overlays/starting-soon/main.js:87` calls `GET https://aquilo.gg/api/schedule` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/aquilo.gg/api/schedule` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10${path} (discord-bot/guild-builder.js:23)
`discord-bot/guild-builder.js:23` calls `GET https://discord.com/api/v10${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10${path} (discord-bot/guild-features.js:72)
`discord-bot/guild-features.js:72` calls `GET https://discord.com/api/v10${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10${path} (discord-bot/temp-vc.js:39)
`discord-bot/temp-vc.js:39` calls `GET https://discord.com/api/v10${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10${path} (discord-bot/tickets.js:46)
`discord-bot/tickets.js:46` calls `GET https://discord.com/api/v10${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10${p} (discord-bot/worker.js:6400)
`discord-bot/worker.js:6400` calls `GET https://discord.com/api/v10${p}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/<p>` 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 https://discord.com/api/v10/channels/${channelId}/webhooks (discord-bot/chat-relay.js:136)
`discord-bot/chat-relay.js:136` calls `GET https://discord.com/api/v10/channels/${channelId}/webhooks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/webhooks` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=${scanLimit} (discord-bot/worker.js:5367)
`discord-bot/worker.js:5367` calls `GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=${scanLimit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/ch…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=50 (discord-bot/worker.js:4431)
`discord-bot/worker.js:4431` calls `GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/webhooks (discord-bot/printerbot.js:33)
`discord-bot/printerbot.js:33` calls `GET https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/webhooks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/webhoo…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/channels/${encodeURIComponent(liveChannelId)} (discord-bot/worker.js:3331)
`discord-bot/worker.js:3331` calls `GET https://discord.com/api/v10/channels/${encodeURIComponent(liveChannelId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/channels/${rulesCh.id}/messages?limit=50 (discord-bot/worker.js:5909)
`discord-bot/worker.js:5909` calls `GET https://discord.com/api/v10/channels/${rulesCh.id}/messages?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/channel-hubs.js:220)
`discord-bot/channel-hubs.js:220` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/cn-games-list-hub.js:174)
`discord-bot/cn-games-list-hub.js:174` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/chan…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/community.js:207)
`discord-bot/community.js:207` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/lfg-hub.js:166)
`discord-bot/lfg-hub.js:166` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/onboarding.js:1011)
`discord-bot/onboarding.js:1011` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/web.js:1070)
`discord-bot/web.js:1070` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:4514)
`discord-bot/worker.js:4514` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:5035)
`discord-bot/worker.js:5035` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:5142)
`discord-bot/worker.js:5142` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(discordId)} (discord-bot/web.js:1068)
`discord-bot/web.js:1068` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(discordId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)} (discord-bot/aquilo/self-roles.js:315)
`discord-bot/aquilo/self-roles.js:315` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized pat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/gifter-roles.js:412)
`discord-bot/gifter-roles.js:412` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/onboarding.js:1106)
`discord-bot/onboarding.js:1106` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/onboarding.js:1179)
`discord-bot/onboarding.js:1179` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/web.js:1069)
`discord-bot/web.js:1069` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/worker.js:5010)
`discord-bot/worker.js:5010` calls `GET https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules (discord-bot/worker.js:6586)
`discord-bot/worker.js:6586` calls `GET https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/auto-moderation/rules…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:5604)
`discord-bot/worker.js:5604` calls `GET https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:5741)
`discord-bot/worker.js:5741` calls `GET https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:5871)
`discord-bot/worker.js:5871` calls `GET https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:6101)
`discord-bot/worker.js:6101` calls `GET https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/members/${discordId} (discord-bot/actor-name.js:45)
`discord-bot/actor-name.js:45` calls `GET https://discord.com/api/v10/guilds/${guildId}/members/${discordId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/members/<p>` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/members/${userId} (discord-bot/chat-relay.js:110)
`discord-bot/chat-relay.js:110` calls `GET https://discord.com/api/v10/guilds/${guildId}/members/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/members/<p>` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/members/${userId} (discord-bot/community-checkin.js:227)
`discord-bot/community-checkin.js:227` calls `GET https://discord.com/api/v10/guilds/${guildId}/members/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/members/<p>` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/guilds/${guildId}/members/${userId} (discord-bot/stream-checkin.js:288)
`discord-bot/stream-checkin.js:288` calls `GET https://discord.com/api/v10/guilds/${guildId}/members/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/members/<p>` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://do/sse (discord-bot/worker.js:2516)
`discord-bot/worker.js:2516` calls `GET https://do/sse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/do/sse` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.microsoft.com/v1.0/me (discord-bot/progression/oauth/xbox.js:18)
`discord-bot/progression/oauth/xbox.js:18` calls `GET https://graph.microsoft.com/v1.0/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.microsoft.com/v1.0/me` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://id.twitch.tv/oauth2/validate (discord-bot/twitch-helix.js:308)
`discord-bot/twitch-helix.js:308` calls `GET https://id.twitch.tv/oauth2/validate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/validate` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://id.twitch.tv/oauth2/validate (discord-bot/twitch-oauth.js:176)
`discord-bot/twitch-oauth.js:176` calls `GET https://id.twitch.tv/oauth2/validate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/validate` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://oauth.battle.net/userinfo (discord-bot/progression/oauth/battlenet.js:13)
`discord-bot/progression/oauth/battlenet.js:13` calls `GET https://oauth.battle.net/userinfo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth.battle.net/userinfo` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://open.tiktokapis.com/v2/user/info/?fields=open_id,union_id,avatar_url,display_name,username (discord-bot/progression/oauth/tiktok.js:13)
`discord-bot/progression/oauth/tiktok.js:13` calls `GET https://open.tiktokapis.com/v2/user/info/?fields=open_id,union_id,avatar_url,display_name,username` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/open.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://site.api.espn.com/apis/site/v2/sports/${sport}/${league}/scoreboard (discord-bot/bet.js:54)
`discord-bot/bet.js:54` calls `GET https://site.api.espn.com/apis/site/v2/sports/${sport}/${league}/scoreboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/site.api.espn.com/apis/site/v2/sports/<p>/<p>/sco…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://store.steampowered.com/api/appdetails?appids=${id}&filters=basic&cc=us (discord-bot/schedule.js:84)
`discord-bot/schedule.js:84` calls `GET https://store.steampowered.com/api/appdetails?appids=${id}&filters=basic&cc=us` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/store.steampowered.com/api/appdetails` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/youtube/v3/channels?part=snippet&mine=true (discord-bot/progression/oauth/youtube.js:14)
`discord-bot/progression/oauth/youtube.js:14` calls `GET https://www.googleapis.com/youtube/v3/channels?part=snippet&mine=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/youtube/v3/cha…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${channelId} (discord-bot/worker.js:6247)
`discord-bot/worker.js:6247` calls `PATCH https://discord.com/api/v10/channels/${channelId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${channelId}/messages/${existing} (discord-bot/worker.js:3090)
`discord-bot/worker.js:3090` calls `PATCH https://discord.com/api/v10/channels/${channelId}/messages/${existing}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages/<p>` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${channelId}/messages/${messageId} (discord-bot/live-status-embed.js:101)
`discord-bot/live-status-embed.js:101` calls `PATCH https://discord.com/api/v10/channels/${channelId}/messages/${messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/mes…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${channelId}/messages/${prior.messageId} (discord-bot/vote-hub.js:334)
`discord-bot/vote-hub.js:334` calls `PATCH https://discord.com/api/v10/channels/${channelId}/messages/${prior.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messag…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${encodeURIComponent(channel.id)} (discord-bot/worker.js:5093)
`discord-bot/worker.js:5093` calls `PATCH https://discord.com/api/v10/channels/${encodeURIComponent(channel.id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=50 (discord-bot/worker.js:2887)
`discord-bot/worker.js:2887` calls `PATCH https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${encodeURIComponent(lfg.channelId)}/messages/${encodeURIComponent(lfg.messageId)} (discord-bot/lfg.js:105)
`discord-bot/lfg.js:105` calls `PATCH https://discord.com/api/v10/channels/${encodeURIComponent(lfg.channelId)}/messages/${encodeURIComponent(lfg.messageId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/di…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/channels/${existing.channelId}/messages/${existing.messageId} (discord-bot/community-checkin.js:990)
`discord-bot/community-checkin.js:990` calls `PATCH https://discord.com/api/v10/channels/${existing.channelId}/messages/${existing.messageId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v1…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)} (discord-bot/voice-temp.js:76)
`discord-bot/voice-temp.js:76` calls `PATCH https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules/${occupant.id} (discord-bot/worker.js:6639)
`discord-bot/worker.js:6639` calls `PATCH https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules/${occupant.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/auto…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://accounts.spotify.com/api/token (discord-bot/rotation.js:219)
`discord-bot/rotation.js:219` calls `POST https://accounts.spotify.com/api/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/accounts.spotify.com/api/token` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (discord-bot/scratch-off.js:1284)
`discord-bot/scratch-off.js:1284` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (discord-bot/sfdock.js:39)
`discord-bot/sfdock.js:39` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${ch.id}/messages (discord-bot/onboarding.js:1224)
`discord-bot/onboarding.js:1224` calls `POST https://discord.com/api/v10/channels/${ch.id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/activity-feed.js:148)
`discord-bot/activity-feed.js:148` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/challenges.js:291)
`discord-bot/challenges.js:291` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/cn-games-list-hub.js:95)
`discord-bot/cn-games-list-hub.js:95` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/community-checkin.js:481)
`discord-bot/community-checkin.js:481` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/live-status-embed.js:88)
`discord-bot/live-status-embed.js:88` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/schedule-rotation.js:187)
`discord-bot/schedule-rotation.js:187` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/spire.js:387)
`discord-bot/spire.js:387` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/stream-events.js:155)
`discord-bot/stream-events.js:155` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/twitch-events.js:203)
`discord-bot/twitch-events.js:203` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/vote-hub.js:354)
`discord-bot/vote-hub.js:354` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/vote-hub.js:466)
`discord-bot/vote-hub.js:466` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/vote-hub.js:528)
`discord-bot/vote-hub.js:528` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/worker.js:1961)
`discord-bot/worker.js:1961` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/messages (discord-bot/worker.js:3110)
`discord-bot/worker.js:3110` calls `POST https://discord.com/api/v10/channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${channelId}/webhooks (discord-bot/chat-relay.js:143)
`discord-bot/chat-relay.js:143` calls `POST https://discord.com/api/v10/channels/${channelId}/webhooks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/webhooks` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/cn-games-roster.js:233)
`discord-bot/cn-games-roster.js:233` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/lfg-hub.js:463)
`discord-bot/lfg-hub.js:463` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/lfg.js:90)
`discord-bot/lfg.js:90` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:2924)
`discord-bot/worker.js:2924` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:4467)
`discord-bot/worker.js:4467` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:4616)
`discord-bot/worker.js:4616` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:4692)
`discord-bot/worker.js:4692` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:4859)
`discord-bot/worker.js:4859` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages (discord-bot/worker.js:5416)
`discord-bot/worker.js:5416` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/webhooks (discord-bot/printerbot.js:65)
`discord-bot/printerbot.js:65` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/webhooks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/webho…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(modLog)}/messages (discord-bot/aquilo/self-roles.js:328)
`discord-bot/aquilo/self-roles.js:328` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(modLog)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${encodeURIComponent(modLog)}/messages (discord-bot/onboarding.js:705)
`discord-bot/onboarding.js:705` calls `POST https://discord.com/api/v10/channels/${encodeURIComponent(modLog)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/message…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${env.PATRON_OF_MONTH_CHANNEL_ID}/messages (discord-bot/patron-of-month.js:115)
`discord-bot/patron-of-month.js:115` calls `POST https://discord.com/api/v10/channels/${env.PATRON_OF_MONTH_CHANNEL_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${recapChannelId}/messages (discord-bot/weekly-recap.js:184)
`discord-bot/weekly-recap.js:184` calls `POST https://discord.com/api/v10/channels/${recapChannelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${rulesCh.id}/messages (discord-bot/worker.js:5950)
`discord-bot/worker.js:5950` calls `POST https://discord.com/api/v10/channels/${rulesCh.id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/channels/${rulesCh.id}/messages (discord-bot/worker.js:5973)
`discord-bot/worker.js:5973` calls `POST https://discord.com/api/v10/channels/${rulesCh.id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/messages` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/voice-temp.js:58)
`discord-bot/voice-temp.js:58` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:3361)
`discord-bot/worker.js:3361` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:5048)
`discord-bot/worker.js:5048` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:5076)
`discord-bot/worker.js:5076` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels (discord-bot/worker.js:5155)
`discord-bot/worker.js:5155` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/preview (discord-bot/welcome.js:61)
`discord-bot/welcome.js:61` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/preview` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/gifter-roles.js:448)
`discord-bot/gifter-roles.js:448` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/onboarding.js:1138)
`discord-bot/onboarding.js:1138` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles (discord-bot/worker.js:5017)
`discord-bot/worker.js:5017` calls `POST https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/roles` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules (discord-bot/worker.js:6614)
`discord-bot/worker.js:6614` calls `POST https://discord.com/api/v10/guilds/${guildId}/auto-moderation/rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/auto-moderation/rule…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:5765)
`discord-bot/worker.js:5765` calls `POST https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${guildId}/channels (discord-bot/worker.js:5881)
`discord-bot/worker.js:5881` calls `POST https://discord.com/api/v10/guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/channels` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/guilds/${g}/scheduled-events (discord-bot/stream-events.js:110)
`discord-bot/stream-events.js:110` calls `POST https://discord.com/api/v10/guilds/${g}/scheduled-events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/guilds/<p>/scheduled-events` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/users/@me/channels (discord-bot/onboarding.js:1212)
`discord-bot/onboarding.js:1212` calls `POST https://discord.com/api/v10/users/@me/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/users/@me/channels` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/users/@me/channels (discord-bot/worker.js:4809)
`discord-bot/worker.js:4809` calls `POST https://discord.com/api/v10/users/@me/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/users/@me/channels` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://do/broadcast (discord-bot/aquilo/overlay-do.js:86)
`discord-bot/aquilo/overlay-do.js:86` calls `POST https://do/broadcast` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/do/broadcast` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://do/publish (discord-bot/activity-do.js:120)
`discord-bot/activity-do.js:120` calls `POST https://do/publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/do/publish` 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 https://id.twitch.tv/oauth2/token (discord-bot/ext-loadout.js:26)
`discord-bot/ext-loadout.js:26` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://id.twitch.tv/oauth2/token (discord-bot/punchcard.js:251)
`discord-bot/punchcard.js:251` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://id.twitch.tv/oauth2/token (discord-bot/punchcard.js:443)
`discord-bot/punchcard.js:443` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://id.twitch.tv/oauth2/token (discord-bot/twitch-helix.js:128)
`discord-bot/twitch-helix.js:128` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://id.twitch.tv/oauth2/token (discord-bot/twitch-helix.js:71)
`discord-bot/twitch-helix.js:71` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://id.twitch.tv/oauth2/token (discord-bot/twitch-oauth.js:147)
`discord-bot/twitch-oauth.js:147` calls `POST https://id.twitch.tv/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/id.twitch.tv/oauth2/token` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.patreon.com/api/oauth2/token (aquilo-gg/worker/loadout-link-worker.js:77)
`aquilo-gg/worker/loadout-link-worker.js:77` calls `POST https://www.patreon.com/api/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.patreon.com/api/oauth2/token` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/applications/${appId}/guilds/${guildId}/commands (discord-bot/worker.js:2795)
`discord-bot/worker.js:2795` calls `PUT https://discord.com/api/v10/applications/${appId}/guilds/${guildId}/commands` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/applications/<p>/guilds…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${channelId}/messages/${messageId}/reactions/${encodeURIComponent(emoji)}/@me (discord-bot/twitch-clips.js:79)
`discord-bot/twitch-clips.js:79` calls `PUT https://discord.com/api/v10/channels/${channelId}/messages/${messageId}/reactions/${encodeURIComponent(emoji)}/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/d…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${channelId}/pins/${j.id} (discord-bot/vote-hub.js:535)
`discord-bot/vote-hub.js:535` calls `PUT https://discord.com/api/v10/channels/${channelId}/pins/${j.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/pins/<p>` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${encodeURIComponent(category.id)}/permissions/${encodeURIComponent(ov.id)} (discord-bot/worker.js:5064)
`discord-bot/worker.js:5064` calls `PUT https://discord.com/api/v10/channels/${encodeURIComponent(category.id)}/permissions/${encodeURIComponent(ov.id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${encodeURIComponent(channel.id)}/permissions/${encodeURIComponent(ov.id)} (discord-bot/worker.js:5172)
`discord-bot/worker.js:5172` calls `PUT https://discord.com/api/v10/channels/${encodeURIComponent(channel.id)}/permissions/${encodeURIComponent(ov.id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/pins/${encodeURIComponent(messageId)} (discord-bot/worker.js:2936)
`discord-bot/worker.js:2936` calls `PUT https://discord.com/api/v10/channels/${encodeURIComponent(channelId)}/pins/${encodeURIComponent(messageId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${encodeURIComponent(t.id)}/permissions/${encodeURIComponent(guildId)} (discord-bot/worker.js:4541)
`discord-bot/worker.js:4541` calls `PUT https://discord.com/api/v10/channels/${encodeURIComponent(t.id)}/permissions/${encodeURIComponent(guildId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${encodeURIComponent(t.id)}/permissions/${encodeURIComponent(roleId)} (discord-bot/worker.js:4551)
`discord-bot/worker.js:4551` calls `PUT https://discord.com/api/v10/channels/${encodeURIComponent(t.id)}/permissions/${encodeURIComponent(roleId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)} (discord-bot/level-tier-roles.js:99)
`discord-bot/level-tier-roles.js:99` calls `PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)} (discord-bot/onboarding.js:692)
`discord-bot/onboarding.js:692` calls `PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members/${encodeURIComponent(userId)}/roles/${encodeURIComponent(roleId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members?limit=1000&after=${after} (discord-bot/gifter-roles.js:331)
`discord-bot/gifter-roles.js:331` calls `PUT https://discord.com/api/v10/guilds/${encodeURIComponent(guildId)}/members?limit=1000&after=${after}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/guilds/${env.AQUILO_VAULT_GUILD_ID}/members/${winner.userId}/roles/${env.PATRON_OF_MONTH_ROLE_ID} (discord-bot/patron-of-month.js:136)
`discord-bot/patron-of-month.js:136` calls `PUT https://discord.com/api/v10/guilds/${env.AQUILO_VAULT_GUILD_ID}/members/${winner.userId}/roles/${env.PATRON_OF_MONTH_ROLE_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for match…
Dangling fetchFetch
high System graph security auth conf 1.00 Flask mutation route `auth_start` without `@login_required` — companion-streamkey/local_server.py:353
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
companion-streamkey/local_server.py:353 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `details` without `@login_required` — companion-streamkey/local_server.py:314
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
companion-streamkey/local_server.py:314 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `end` without `@login_required` — companion-streamkey/local_server.py:343
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
companion-streamkey/local_server.py:343 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `start` without `@login_required` — companion-streamkey/local_server.py:321
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
companion-streamkey/local_server.py:321 securityAuth flask unauth route
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/bulk-regen-cards.py:73
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/bulk-regen-cards.py:73 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/fix-card-brand-A.py:30
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/fix-card-brand-A.py:30 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/gear-worn-overlay-pipeline.py:253
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/gear-worn-overlay-pipeline.py:253 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/gen-expansion-art.py:97
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/gen-expansion-art.py:97 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/overhaul-upload.py:84
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/overhaul-upload.py:84 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/rembg-pipeline.py:158
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/rembg-pipeline.py:158 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/upload-arena-polish-fx.py:33
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/upload-arena-polish-fx.py:33 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/upload-damage-numbers.py:39
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/upload-damage-numbers.py:39 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in discord-bot/tools/upload-pixel-art-v9.py:96
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
discord-bot/tools/upload-pixel-art-v9.py:96 Subprocess shell true
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — aquilo-gg/overlays/gift-jar/main.js:123
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 — aquilo-gg/overlays/hangman/main.js:190
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 — aquilo-gg/worker/loadout-link-worker.js:77
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 — discord-bot/admin-menu.js:491
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 — discord-bot/aquilo/checkin-slash.js:83
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 — discord-bot/aquilo/community-chat.js:287
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 — discord-bot/aquilo/notify.js: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 — discord-bot/aquilo/overlay-do.js:39
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 — discord-bot/aquilo/products.js:6
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 — discord-bot/aquilo/self-roles.js:315
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 — discord-bot/aquilo/spotlight.js: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 — discord-bot/aquilo/util.js:47
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 — discord-bot/aquilo/worker.js:151
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 — discord-bot/channel-hubs.js:190
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 — discord-bot/chat-relay.js:136
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 — discord-bot/cn-games-list-hub.js:95
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 — discord-bot/cn-games-roster.js:233
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 — discord-bot/cn-vote-hub.js:81
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 — discord-bot/community-checkin.js:369
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 — discord-bot/counting-purge.js:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — discord-bot/daily-bonus-push.js: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 — discord-bot/discord-cleanup.js:73
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 — discord-bot/game-art-finder.js: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 — discord-bot/gifter-roles.js:331
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 — discord-bot/guild-features.js:72
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 — discord-bot/level-tier-roles.js:99
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 — discord-bot/lfg-hub.js:134
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 — discord-bot/onboarding.js:200
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 — discord-bot/printerbot.js:33
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 — discord-bot/progression/oauth/_generic.js:59
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 — discord-bot/progression/oauth/battlenet.js: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 — discord-bot/progression/oauth/epic.js: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 — discord-bot/progression/oauth/steam.js:62
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 — discord-bot/progression/oauth/tiktok.js: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 — discord-bot/progression/oauth/twitch.js: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 — discord-bot/progression/oauth/xbox.js: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 — discord-bot/progression/oauth/youtube.js: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 — discord-bot/punchcard.js:251
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 — discord-bot/push.js:39
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 — discord-bot/queue.js:461
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 — discord-bot/register-commands.js: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 — discord-bot/schedule-rotation.js: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 — discord-bot/scheduled-messages.js:290
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 — discord-bot/scratch-off.js:1284
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 — discord-bot/sfdock.js:39
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 — discord-bot/spire.js:473
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 — discord-bot/stream-events.js:110
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 — discord-bot/support-tickets.js:1085
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 — discord-bot/tools/replicate-card-samples.mjs:58
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 — discord-bot/tools/replicate-card-styled-retry.mjs: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 — discord-bot/tools/replicate-card-styled.mjs: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 — discord-bot/tools/replicate-gwyf-overlay-assets.mjs: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 — discord-bot/twitch-helix.js: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 — discord-bot/twitch-oauth.js:147
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 — discord-bot/vote-hub.js:334
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 — discord-bot/web.js:1068
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 — discord-bot/weekly-recap.js:184
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 — discord-bot/welcome.js:61
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 — discord-bot/worker.js:114
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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/companion-streamkey-release.yml:82
.github/workflows/release.yml:127
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 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/companion-streamkey-release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in aquilo-gg/worker/loadout-link-worker.js:48
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
aquilo-gg/worker/loadout-link-worker.js:48 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/activity-do.js:73
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/activity-do.js:73 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/activity-feed.js:179
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/activity-feed.js:179 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/aquilo/today-game.js:107
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/aquilo/today-game.js:107 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/aquilo/worker.js:358
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/aquilo/worker.js:358 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/boltbound-emotes.js:153
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/boltbound-emotes.js:153 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/boltbound-replays-rx.js:198
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/boltbound-replays-rx.js:198 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/cards-web.js:186
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/cards-web.js:186 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/challenges.js:392
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/challenges.js:392 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/character.js:214
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/character.js:214 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/community.js:20
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/community.js:20 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/daily-quests.js:489
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/daily-quests.js:489 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/death-counter.js:184
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/death-counter.js:184 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/ext-bets.js:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/ext-bets.js:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/ext-quick.js:47
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/ext-quick.js:47 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/ext-shared.js:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/ext-shared.js:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/ext.js:54
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/ext.js:54 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/friends.js:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/friends.js:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/lfg.js:229
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/lfg.js:229 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/partyup.js:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/partyup.js:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/powerdeck.js:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/powerdeck.js:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/progression/http.js:29
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/progression/http.js:29 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/punchcard.js:41
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/punchcard.js:41 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/schedule.js:297
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/schedule.js:297 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/scratch-off.js:336
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/scratch-off.js:336 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/sf-community.js:464
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/sf-community.js:464 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/sfdock.js:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/sfdock.js:16 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/spire-map.js:633
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/spire-map.js:633 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in discord-bot/worker.js:767
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
discord-bot/worker.js:767 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/link/main.js:140
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/link/main.js:140 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/apex/main.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/apex/main.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/bolts/main.js:82
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/bolts/main.js:82 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/check-in/main.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/check-in/main.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/clash/main.js:144
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/clash/main.js:144 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/commands/main.js:158
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/commands/main.js:158 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/compact/main.js:277
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/compact/main.js:277 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/counters/main.js:60
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/counters/main.js:60 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/follow-gwyf/index.html:296
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/follow-gwyf/index.html:296 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/follow-minecraft/index.html:286
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/follow-minecraft/index.html:286 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/gift-jar/main.js:719
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/gift-jar/main.js:719 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/goals/main.js:30
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/goals/main.js:30 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/hangman/main.js:216
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/hangman/main.js:216 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/minigames/main.js:62
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/minigames/main.js:62 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/recap/main.js:40
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/recap/main.js:40 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/starting-soon/main.js:46
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/starting-soon/main.js:46 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/tanks/main.js:131
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/tanks/main.js:131 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in aquilo-gg/overlays/viewer/main.js:95
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
aquilo-gg/overlays/viewer/main.js:95 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in discord-bot/tools/post-announcement.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
discord-bot/tools/post-announcement.mjs:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in discord-bot/tools/post-cvn-poll.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
discord-bot/tools/post-cvn-poll.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in discord-bot/tools/post-schedule-poll.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
discord-bot/tools/post-schedule-poll.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in discord-bot/tools/repoint-global-art-cachebust.mjs:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
discord-bot/tools/repoint-global-art-cachebust.mjs:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in discord-bot/tools/xp-checkin-reset.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
discord-bot/tools/xp-checkin-reset.mjs:22 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — companion-streamkey/watchdog_task.py:63
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/arena-polish-fx-generator.py:214
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/bulk-regen-cards.py:145
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/follow-overlay-contact-sheet.py:84
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/gear-worn-feasibility.py:70
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/gear-worn-overlay-pipeline.py:140
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/gen-expansion-art.py:135
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/minigames-pixel-art.py:115
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/overhaul-generate.py:69
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/overhaul-upload.py:84
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/pixel-card-pipeline-v4.py:160
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/pixel-frame-generator-v2.py:117
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/pixel-frame-generator.py:129
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/premium-card-pipeline.py:140
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/rembg-pipeline.py:188
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/upload-arena-polish-fx.py:33
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/upload-damage-numbers.py:39
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — discord-bot/tools/upload-pixel-art-v9.py:66
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 129 placeholder/mock markers across 53 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 591 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 7 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.
3 files, 7 locations
.github/workflows/build.yml:27, 30, 58 (3 hits)
.github/workflows/post-release-notes.yml:47, 50 (2 hits)
.github/workflows/release.yml:47, 53 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
52 tests / 389 src (ratio 0.13).
low System graph quality Integrity conf 1.00 12 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: discord-bot/tools/rembg-pipeline.py:rembg, discord-bot/tools/follow-overlay-contact-sheet.py:rembg This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're …
12 occurrences
repo-level (12 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: discord-bot/tools/pixel-card-pipeline-v4.py:main, discord-bot/tools/pixel-card-pipeline-v5.py:main, discord-bot/tools/pixel-card-pipeline.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code…
5 occurrences
repo-level (5 hits)
duplicatesduplication

Showing first 300 of 351. Refine filters or use the findings page for deep search.

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/c89126db-802c-4fac-9bff-de6882099183/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c89126db-802c-4fac-9bff-de6882099183/

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.