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.

bohemian-miser/RecipeLanes

https://github.com/bohemian-miser/RecipeLanes · scanned 2026-06-17 01:42 UTC (1 month, 1 week ago)

181 raw signals (0 security + 181 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -18.9 (diff) · 170 actionable findings from 1 signal source. 11 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 · 170 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 19 Low 115 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 170 Crowd 0 Layer: Api 1 Frontend 124 Security 5 Cicd 3 Quality 37

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 57.8/100 with 100.0% coverage. It contains 1037 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 181 findings — concentrated in frontend (124), quality (37), cicd (14). Risk profile is high: 1 critical, 0 high, 20 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 134 of 170 actionable findings. 181 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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — recipe-lanes/components/auth-provider.tsx:76

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 — recipe-lanes/e2e/utils/admin-utils.ts:144

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 — recipe-lanes/lib/ai-service.ts:85

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 — recipe-lanes/scripts/backfill-icon-index.ts:43

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — recipe-lanes/scripts/backfill-icon-search-terms.ts:86

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 — recipe-lanes/scripts/backfill-search-terms.ts:63

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 — recipe-lanes/scripts/backfill-vertex-embedding.ts: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 — recipe-lanes/scripts/eval-icon-vision-terms.ts:64

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — recipe-lanes/scripts/fetch-real-icons.ts: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 — recipe-lanes/scripts/search-test.ts:22

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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

CLAUDE.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/verify-app/SKILL.md

skills/verify-app/SKILL.md VerificationSkill file

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

google-github-actions/auth@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 42, 48

.github/workflows/deploy-backend.yml:42, 48 (2 hits)

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in recipe-lanes/scripts/investigation/cloud-timeline.ts:6

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

recipe-lanes/scripts/investigation/cloud-timeline.ts:6 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in recipe-lanes/scripts/investigation/quick-log-fetch.ts:1

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

recipe-lanes/scripts/investigation/quick-log-fetch.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in recipe-lanes/scripts/investigation/recipe-logs.ts:45

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

recipe-lanes/scripts/investigation/recipe-logs.ts:45 Node child process

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

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

Found 38 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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

Found 900 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 11 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, 11 locations

.github/workflows/ci.yml:31, 34, 60, 63, 73, 111, 114, 123, +1 more (9 hits)

.github/workflows/compute-umap.yml:26

.github/workflows/deploy-backend.yml:25

CI/CD securitySupply chainGithub actions

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `staging_backup` in recipe-lanes/scripts/backup-staging.ts:24

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

recipe-lanes/package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 React Flow <Controls> without dark theming — recipe-lanes/components/recipe-lanes/react-flow-diagram.tsx:818

`<Controls>` ships with white buttons. Override `.react-flow__controls` and `.react-flow__controls-button` in your stylesheet or pass a styled wrapper. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.controls.no-bg

Fq controls no bg

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — recipe-lanes/app/actions.ts:160