Abdulberk/circuit-forge — Repobility public scan

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

Abdulberk/circuit-forge

https://github.com/Abdulberk/circuit-forge · scanned 2026-06-17 01:12 UTC (1 month, 2 weeks ago)

40 raw signals (0 security + 40 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +13.8 (diff) · 40 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

100.0% cov · 40 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 10 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 40 Crowd 0 Layer: Frontend 5 Security 7 Quality 28

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

Showing 22 of 40 actionable findings. 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 — apps/api/src/parts/parts.service.ts:94

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 security security conf 1.00 Insecure pattern 'node_child_process' in apps/api/src/generation/circuit-simulator.service.ts:17

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

apps/api/src/generation/circuit-simulator.service.ts:17 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/worker-sim/src/simulation/runner.ts:5

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

apps/worker-sim/src/simulation/runner.ts:5 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/coverage-matrix.mjs:11

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

scripts/coverage-matrix.mjs:11 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/fuzz-circuits.mjs:11

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

scripts/fuzz-circuits.mjs:11 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/pairwise-sweep.mjs:14

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

scripts/pairwise-sweep.mjs:14 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/sim-run.mjs:8

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

scripts/sim-run.mjs:8 Node child process

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

13 test file(s) for 144 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `AI_LIVE`, `CORS_ORIGINS`, `DB_CONNECTION_LIMIT`, `ENABLE_SWAGGER`, `NGSPICE_BIN`, `NGSPICE_PATH`, `SIMLOOP_LIVE`, `TME_LIVE` + 1 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

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

Found 43 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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/api/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

apps/api/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/worker-sim/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

apps/worker-sim/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/eda-core/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/eda-core/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/llm-core/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/llm-core/package.json LockfileReproducibilityGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/api/__tests__/e2e-smoke.test.ts:121

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 — apps/api/prisma/seed.ts:456

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 — apps/api/src/generation/__live__/ai-grounding-live.spec.ts:63

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 — apps/api/src/generation/__live__/sim-loop-integration.live.spec.ts:132

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 — apps/api/src/main.ts:77

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 quality Complexity conf 1.00 Very large file: packages/eda-core/__tests__/active-devices.test.ts (902 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: packages/eda-core/__tests__/digital-devices.test.ts (967 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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/4cf3ea9d-1dce-4b79-8a0e-0d0111f7602c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4cf3ea9d-1dce-4b79-8a0e-0d0111f7602c/

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.