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

ZackMFleischman/ai-experiments

https://github.com/ZackMFleischman/ai-experiments · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

79 raw signals (0 security + 79 graph)

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

Complete repo analysis

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

JSON
Combined
71.3
/100
Security checks
71
0 findings
System graph
71
88.9% cov · 79 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 8 Medium 30 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 79 Crowd 0 Layer: Frontend 1 Security 21 Cicd 1 Quality 43 Api 13
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.3/100 with 88.9% coverage. It contains 1054 nodes across 5 cross-layer flows, written primarily in mixed languages. Engine surfaced 79 findings — concentrated in quality (43), security (21), api (13). Risk profile is high: 0 critical, 8 high, 30 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 51 of 79 actionable findings. 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 /loom/state-list/${StateDir.projects} (loom/packages/engine-app/src/main.ts:375)
`loom/packages/engine-app/src/main.ts:375` calls `GET /loom/state-list/${StateDir.projects}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state-list/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /loom/state/${name} (loom/packages/engine-app/src/state.ts:65)
`loom/packages/engine-app/src/state.ts:65` calls `GET /loom/state/${name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /loom/state/${StateDir.fixtures}/${encodeURIComponent(name)} (loom/packages/engine-app/src/main.ts:412)
`loom/packages/engine-app/src/main.ts:412` calls `GET /loom/state/${StateDir.fixtures}/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /loom/state/${StateDir.projects}/${encodeURIComponent(name)} (loom/packages/engine-app/src/main.ts:549)
`loom/packages/engine-app/src/main.ts:549` calls `GET /loom/state/${StateDir.projects}/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /loom/effects/${encodeURIComponent(name)} (loom/packages/engine-app/src/main.ts:305)
`loom/packages/engine-app/src/main.ts:305` calls `POST /loom/effects/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/effects/<p>` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /loom/state/${name} (loom/packages/engine-app/src/state.ts:82)
`loom/packages/engine-app/src/state.ts:82` calls `POST /loom/state/${name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /loom/state/${StateDir.fixtures}/${encodeURIComponent(r.name)} (loom/packages/engine-app/src/main.ts:513)
`loom/packages/engine-app/src/main.ts:513` calls `POST /loom/state/${StateDir.fixtures}/${encodeURIComponent(r.name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>/<p>` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /loom/state/${StateDir.projects}/${encodeURIComponent(name)} (loom/packages/engine-app/src/main.ts:538)
`loom/packages/engine-app/src/main.ts:538` calls `POST /loom/state/${StateDir.projects}/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/loom/state/<p>/<p>` If this points at an external A…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — loom/content/test/setup.ts:2
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 — loom/packages/engine-app/src/main.ts:412
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 — loom/scripts/validate-m3.mjs:178
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 — loom/scripts/validate-m9.mjs:250
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: loom/.mcp.json
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.
loom/.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 GitHub Action is tag-pinned rather than SHA-pinned
marocchino/sticky-pull-request-comment@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/loom-ci.yml:125 CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/packages/engine-app/vite.config.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/packages/engine-app/vite.config.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/affected-shots.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/affected-shots.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/shoot.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/shoot.mjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-fixtures.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-fixtures.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-layers.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-layers.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m0.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m0.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m1.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m1.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m11.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m11.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m2.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m2.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m3.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m3.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m4.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m4.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m5.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m5.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m6.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m6.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m7.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m7.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m8.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m8.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-m9.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-m9.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-modulators.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-modulators.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-panic.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-panic.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-projects.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-projects.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in loom/scripts/validate-stdlib.mjs:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
loom/scripts/validate-stdlib.mjs:7 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 17 placeholder/mock markers across 10 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: license, 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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 55 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 Tests conf 1.00 Low test-to-source ratio
46 tests / 213 src (ratio 0.22).
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: loom/packages/engine-app/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.
loom/packages/engine-app/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: loom/packages/runtime/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.
loom/packages/runtime/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: loom/packages/sidecar/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.
loom/packages/sidecar/package.json LockfileReproducibilityGenerated 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 api Wiring conf 1.00 Unused endpoint: USE /loom/effects/
`loom/packages/engine-app/vite.config.ts` declares `USE /loom/effects/` 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: USE /loom/media
`loom/packages/engine-app/vite.config.ts` declares `USE /loom/media` 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: USE /loom/mediafs/
`loom/packages/engine-app/vite.config.ts` declares `USE /loom/mediafs/` 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: USE /loom/state-list/
`loom/packages/engine-app/vite.config.ts` declares `USE /loom/state-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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /loom/state/
`loom/packages/engine-app/vite.config.ts` declares `USE /loom/state/` 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/4908eb8b-6149-4e5b-844e-c0823c26e431/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4908eb8b-6149-4e5b-844e-c0823c26e431/

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.