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.

zkaskoo/F-zzOkosan

https://github.com/zkaskoo/F-zzOkosan · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

51 raw signals (0 security + 51 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 46 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 7 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Frontend 6 Hardware 5 Security 1 Cicd 1 Quality 9 Api 24

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 71.4/100 with 100.0% coverage. It contains 543 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 51 findings — concentrated in api (24), quality (13), frontend (6). Risk profile is low: 0 critical, 0 high, 11 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 41 of 46 actionable findings. 51 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.

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 hardware Security conf 1.00 Dockerfile runs as root: fozzokosan/backend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: fozzokosan/frontend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph quality Integrity conf 1.00 5 occurrences Frontend route `/receptek/:id/szerkesztes` has no Link/navigate to it — fozzokosan/frontend/src/App.tsx

The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.

5 occurrences

repo-level (5 hits)

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in fozzokosan/frontend/src/services/api.ts:37

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

fozzokosan/frontend/src/services/api.ts:37 Local storage auth token

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 24 placeholder/mock markers across 12 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 Tests conf 1.00 Very low test-to-source ratio

1 test file(s) for 114 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 14 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

fozzokosan/frontend/Dockerfile:1 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

fozzokosan/backend/Dockerfile:1 containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/setup-node@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 37, 79

fozzokosan/.github/workflows/ci.yml:37, 79 (2 hits)

CI/CD securitySupply chainGithub actions

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — fozzokosan/backend/prisma/seed.ts:127

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — fozzokosan/backend/src/main.ts:28

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /menu-plans/:id

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /menu-plans/:id/items/:itemId

`fozzokosan/backend/src/menu-plans/menu-plans.controller.ts` declares `DELETE /menu-plans/:id/items/:itemId` 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 o…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /recipes/:id

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /recipes/:recipeId/comments/:commentId

`fozzokosan/backend/src/comments/comments.controller.ts` declares `DELETE /recipes/:recipeId/comments/:commentId` 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 remov…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /shopping-lists/:id

`fozzokosan/backend/src/shopping-lists/shopping-lists.controller.ts` declares `DELETE /shopping-lists/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /users/me

`fozzokosan/backend/src/users/users.controller.ts` declares `DELETE /users/me` 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 /ingredients/search

`fozzokosan/backend/src/ingredients/ingredients.controller.ts` declares `GET /ingredients/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenti…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /menu-plans/:id

`fozzokosan/backend/src/menu-plans/menu-plans.controller.ts` declares `GET /menu-plans/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /nlp/status

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /recipes/:slugOrId

`fozzokosan/backend/src/recipes/recipes.controller.ts` declares `GET /recipes/:slugOrId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /shopping-lists/:id

`fozzokosan/backend/src/shopping-lists/shopping-lists.controller.ts` declares `GET /shopping-lists/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or doc…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /units/convert

`fozzokosan/backend/src/units/units.controller.ts` declares `GET /units/convert` 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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /units/supported

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

Unused endpoint

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

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /users/me

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /recipes/:id

`fozzokosan/backend/src/recipes/recipes.controller.ts` declares `PATCH /recipes/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /shopping-lists/:id/items/:itemId/toggle

`fozzokosan/backend/src/shopping-lists/shopping-lists.controller.ts` declares `PATCH /shopping-lists/:id/items/:itemId/toggle` 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 — c…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /users/me

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

Unused endpoint

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

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

Unused endpoint

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

`fozzokosan/backend/src/auth/auth.controller.ts` declares `POST /auth/register` 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 /menu-plans/:id/items

`fozzokosan/backend/src/menu-plans/menu-plans.controller.ts` declares `POST /menu-plans/:id/items` 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 document…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /menu-plans/:id/shopping-list

`fozzokosan/backend/src/menu-plans/menu-plans.controller.ts` declares `POST /menu-plans/:id/shopping-list` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /nlp/parse-ingredients

`fozzokosan/backend/src/nlp/nlp.controller.ts` declares `POST /nlp/parse-ingredients` 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 consu…

Unused endpoint

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

`fozzokosan/backend/src/upload/upload.controller.ts` declares `POST /uploads/image` 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 consume…

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/1010088d-5a2b-485d-b9f8-b84ab395bd8f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1010088d-5a2b-485d-b9f8-b84ab395bd8f/

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.