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.

builtbyfew/effing

https://github.com/builtbyfew/effing · scanned 2026-06-17 01:44 UTC (1 month, 2 weeks ago)

85 raw signals (0 security + 85 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 79 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 5 Medium 19 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 79 Crowd 0 Layer: Frontend 20 Hardware 1 Security 6 Cicd 5 Quality 36 Api 11

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 51.9/100 with 88.9% coverage. It contains 1177 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 85 findings — concentrated in quality (36), frontend (20), api (11). Risk profile is high: 0 critical, 5 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 11 of 79 actionable findings. 85 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: GET http://127.0.0.1:${proxy.port}/not-a-url (packages/ffs/src/proxy.integration.test.ts:116)

`packages/ffs/src/proxy.integration.test.ts:116` calls `GET http://127.0.0.1:${proxy.port}/not-a-url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/not-a-url` If this points at an external API,…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://fonts.gstatic.com/s/inter/.../Inter-Bold.ttf (packages/dev/src/manual.ts:209)

`packages/dev/src/manual.ts:209` calls `GET https://fonts.gstatic.com/s/inter/.../Inter-Bold.ttf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fonts.gstatic.com/s/inter/.../inter-bold.ttf` If this points at…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: HEAD https://cdnjs.cloudflare.com (packages/canvas/comparison/emoji.test.tsx:24)

`packages/canvas/comparison/emoji.test.tsx:24` calls `HEAD https://cdnjs.cloudflare.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/cdnjs.cloudflare.com` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/ffs/purge (packages/dev/src/server/dev/app/routes/preview.effie.tsx:346)

`packages/dev/src/server/dev/app/routes/preview.effie.tsx:346` calls `POST /api/ffs/purge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ffs/purge` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/ffs/render?scale=${encodeURIComponent(scale)} (packages/dev/src/server/dev/app/routes/preview.effie.tsx:286)

`packages/dev/src/server/dev/app/routes/preview.effie.tsx:286` calls `POST /api/ffs/render?scale=${encodeURIComponent(scale)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ffs/render` If this points at an external…

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: GET /render/:id/progress

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /render/:id/video

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /warmup/:id/progress

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /purge

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /render

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /warmup

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

Unused endpoint

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

For AI agents + API integrations

Email me when this repo regresses

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

API access

This page is publicly accessible at: https://repobility.com/scan/01b6a443-021d-48aa-8af5-1a23bf89dcb5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01b6a443-021d-48aa-8af5-1a23bf89dcb5/

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.