Legcord/Legcord

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.

Scan timing: clone 4.85s · analysis 1.91s · 3.7 MB · GitHub API rate-limit (preflight)

https://github.com/Legcord/Legcord · scanned 2026-05-31 01:22 UTC (5 days, 14 hours ago) · 10 languages

221 findings (51 legacy + 170 scanner) 61st percentile · Typescript · small (2-20K LoC) Scanner says 65 (higher by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · 136 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	96.0	0.25	24.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	76.0	0.15	11.40
`practices_score`	72.0	0.15	10.80
`code_quality`	78.8	0.10	7.88
Overall		1.00	69.1

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 2 High 23 Medium 19 Low 75 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 51 9-layer 85 Crowd 0 Layer: Security 5 Quality 37 Software 40 Frontend 35 Cicd 15 Api 4

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 64.9/100 with 88.9% coverage. It contains 515 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 85 findings — concentrated in frontend (35), software (21), cicd (15). Risk profile is high: 0 critical, 3 high, 15 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 4 of 136 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high 9-layer api wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/Legcord/Legcord/contributors (src/shelter/settings/components/AboutPopup.tsx:23)

`src/shelter/settings/components/AboutPopup.tsx:23` calls `GET https://api.github.com/repos/Legcord/Legcord/contributors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/legcord/legcord/co…

wiringdangling-fetchfetch

high 9-layer api wiring conf 1.00 Dangling fetch: GET https://cdn.discordapp.com/icons/${guildID}/${guildIcon}.png (src/discord/touchbar.ts:53)

`src/discord/touchbar.ts:53` calls `GET https://cdn.discordapp.com/icons/${guildID}/${guildIcon}.png` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/cdn.discordapp.com/icons/<p>/<p>.png` If this points at an …

wiringdangling-fetchfetch

high 9-layer api wiring conf 1.00 Dangling fetch: GET https://legcord.app/latest.json (src/shelter/settings/components/HeroUpdater.tsx:9)

`src/shelter/settings/components/HeroUpdater.tsx:9` calls `GET https://legcord.app/latest.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/legcord.app/latest.json` If this points at an external API, prefi…

wiringdangling-fetchfetch

low 9-layer api wiring conf 1.00 Unused endpoint: DELETE

`src/main.ts` declares `DELETE ` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

wiringunused-endpoint

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/2025d0cc-4d3e-4226-82d5-1af68c4c8592/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2025d0cc-4d3e-4226-82d5-1af68c4c8592/

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.