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

teaarte/loom

https://github.com/teaarte/loom · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

380 raw signals (4 security + 376 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 380 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
74.0
/100
Security checks
74
4 findings
System graph
74
88.9% cov · 376 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 7 Medium 28 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 4 System graph 376 Crowd 0 Layer: Quality 356 Frontend 3 Hardware 2 Security 18 Cicd 1
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 74.0/100 with 88.9% coverage. It contains 2610 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 376 findings — concentrated in quality (352), security (18), frontend (3). Risk profile is high: 0 critical, 5 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high Security checks quality Practices conf 0.84 Foundry mined bad chains: teaarte/loom
Comment chain pattern product: bad_chains Repo: teaarte/loom Thread: teaarte/loom#3 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_verifica…
high Security checks quality Quality conf 0.76 Foundry mined schema ui api mismatch: teaarte/loom
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/kernel/src/sandbox/passthrough.ts:65
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/kernel/src/sandbox/passthrough.ts:65 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/kernel/src/sandbox/path-restricted.ts:32
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/kernel/src/sandbox/path-restricted.ts:32 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/kernel/src/state/transaction.ts:38
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/kernel/src/state/transaction.ts:38 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/kernel/src/types/plugins.ts:358
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/kernel/src/types/plugins.ts:358 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/kernel/src/types/transaction.ts:18
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/kernel/src/types/transaction.ts:18 Exec used
medium Security checks quality maintenance conf 0.70 Foundry mined blueprint gap alignment: teaarte/loom
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: teaarte/loom
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/cli/src/commands/bot.ts:66
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 — packages/daemon/src/notify-channels.ts:159
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 — packages/daemon/src/notify.ts:73
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 — packages/daemon/src/worktree-lifecycle.ts:73
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 — packages/daemon/test/notify.test.ts:68
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 — packages/server/test/http.test.ts:123
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 — packages/server/test/notify-wiring.test.ts:61
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 — packages/server/test/recovery.test.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 — packages/server/test/ship-routes.test.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 — packages/server/test/spawn-transcript.test.ts:61
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 packages/cli/src/commands/daemon.ts:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/commands/daemon.ts:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/commands/serve.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/commands/serve.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/commands/up.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/commands/up.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/launch.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/launch.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/lib/probes.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/lib/probes.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/daemon/src/notify-channels.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/daemon/src/notify-channels.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/daemon/src/worktree-lifecycle.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/daemon/src/worktree-lifecycle.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/checks-executor.ts:36
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/checks-executor.ts:36 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/container-executor.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/container-executor.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/copy.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/copy.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/git-delta.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/git-delta.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/spawn-cli.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/spawn-cli.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/kernel/src/sandbox/passthrough.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/kernel/src/sandbox/passthrough.ts:13 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 43 placeholder/mock markers across 27 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, lockfile. 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/Dockerfile:16 containersPinned dependencies
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/bundles/code/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/bundles/code/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cli/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/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/config/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/config/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/daemon/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/daemon/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/dashboard/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/dashboard/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/driver/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/driver/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/loader/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/loader/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mcp-server/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/mcp-server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/pipeline/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/pipeline/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/providers/anthropic-sdk/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/providers/anthropic-sdk/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/providers/claude-code-shuttle/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/providers/claude-code-shuttle/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/providers/ollama/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/providers/ollama/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/providers/openrouter/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/providers/openrouter/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/server/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/server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/transport-types/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/transport-types/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `pcLegacy` in packages/mcp-server/src/bootstrap.ts:241
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 quality Integrity conf 1.00 Old/deprecated-named symbol `pipeline_backup` in packages/mcp-server/src/server.ts:79
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 quality Integrity conf 1.00 Old/deprecated-named symbol `pipeline_backup` in packages/mcp-server/src/tools/backup.ts:1
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 quality Integrity conf 1.00 Old/deprecated-named symbol `pipeline_backup` in packages/mcp-server/src/types.ts:275
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 quality Integrity conf 1.00 Old/deprecated-named symbol `pipeline_backup` in packages/mcp-server/test/backup-restore.test.ts:132
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 quality Integrity conf 1.00 Old/deprecated-named symbol `pipeline_backup` in packages/mcp-server/test/wire-smoke.test.ts:208
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 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 — packages/cli/test/npm-pack-smoke.test.ts:174
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 — packages/mcp-server/test/ollama-loop.test.ts:156
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 — packages/server/test/fixtures.ts:249
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/bundles/code/src/bundle.ts (1404 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/bundles/code/test/bundle.test.ts (1291 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/kernel/test/fsm.test.ts (2275 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/loader/test/bundle-loader.test.ts (1668 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/mcp-server/test/e2e-shuttle.test.ts (1172 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/2df20ffa-b6b4-4561-b0b9-6177af9ecb4e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2df20ffa-b6b4-4561-b0b9-6177af9ecb4e/

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.