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

anuraagkolli/invariance

https://github.com/anuraagkolli/invariance · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

161 raw signals (0 security + 161 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.2 (diff) · 161 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
63.5
/100
Security checks
64
0 findings
System graph
64
100.0% cov · 161 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 33 Medium 38 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 161 Crowd 0 Layer: Frontend 12 Hardware 2 Security 5 Quality 92 Api 50
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 63.5/100 with 100.0% coverage. It contains 1092 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 161 findings — concentrated in quality (92), api (50), frontend (12). Risk profile is high: 0 critical, 33 high, 38 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 108 of 161 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 /demo-api${path} (apps/console/src/api.ts:172)
`apps/console/src/api.ts:172` calls `GET /demo-api${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/demo-api/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/analytics/summary (apps/control-plane/test/analytics.test.ts:79)
`apps/control-plane/test/analytics.test.ts:79` calls `GET /v1/apps/app1/analytics/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/analytics/summary` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/analytics/summary (apps/control-plane/test/analytics.test.ts:87)
`apps/control-plane/test/analytics.test.ts:87` calls `GET /v1/apps/app1/analytics/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/analytics/summary` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/mods (apps/control-plane/test/analytics.test.ts:97)
`apps/control-plane/test/analytics.test.ts:97` calls `GET /v1/apps/app1/mods` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/mods` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/subjects/u1/overview (apps/control-plane/test/analytics.test.ts:155)
`apps/control-plane/test/analytics.test.ts:155` calls `GET /v1/apps/app1/subjects/u1/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/overview` If this points at an external AP…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/subjects/u1/pointer (apps/control-plane/test/analytics.test.ts:109)
`apps/control-plane/test/analytics.test.ts:109` calls `GET /v1/apps/app1/subjects/u1/pointer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/pointer` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/app1/subjects/u1/pointer (apps/control-plane/test/authoring.test.ts:192)
`apps/control-plane/test/authoring.test.ts:192` calls `GET /v1/apps/app1/subjects/u1/pointer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/pointer` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/apps/demo/subjects/u1/pointer (apps/control-plane/scripts/live-design.ts:71)
`apps/control-plane/scripts/live-design.ts:71` calls `GET /v1/apps/demo/subjects/u1/pointer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/demo/subjects/u1/pointer` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET https://x (apps/control-plane/test/verification.test.ts:240)
`apps/control-plane/test/verification.test.ts:240` calls `GET https://x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/x` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/events (apps/control-plane/test/analytics.test.ts:146)
`apps/control-plane/test/analytics.test.ts:146` calls `POST /v1/apps/app1/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/events` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/events (apps/control-plane/test/analytics.test.ts:150)
`apps/control-plane/test/analytics.test.ts:150` calls `POST /v1/apps/app1/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/events` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/events (apps/control-plane/test/analytics.test.ts:67)
`apps/control-plane/test/analytics.test.ts:67` calls `POST /v1/apps/app1/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/events` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/events (apps/control-plane/test/analytics.test.ts:73)
`apps/control-plane/test/analytics.test.ts:73` calls `POST /v1/apps/app1/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/events` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/manifest (apps/control-plane/test/analytics.test.ts:51)
`apps/control-plane/test/analytics.test.ts:51` calls `POST /v1/apps/app1/manifest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/manifest` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/manifest (apps/control-plane/test/authoring.test.ts:180)
`apps/control-plane/test/authoring.test.ts:180` calls `POST /v1/apps/app1/manifest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/manifest` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/manifest (apps/control-plane/test/authoring.test.ts:199)
`apps/control-plane/test/authoring.test.ts:199` calls `POST /v1/apps/app1/manifest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/manifest` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/manifest (apps/control-plane/test/design-authoring.test.ts:26)
`apps/control-plane/test/design-authoring.test.ts:26` calls `POST /v1/apps/app1/manifest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/manifest` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/mods/${modId}/kill (apps/control-plane/test/analytics.test.ts:114)
`apps/control-plane/test/analytics.test.ts:114` calls `POST /v1/apps/app1/mods/${modId}/kill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/mods/<p>/kill` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/mods/${modId}/kill (apps/control-plane/test/analytics.test.ts:135)
`apps/control-plane/test/analytics.test.ts:135` calls `POST /v1/apps/app1/mods/${modId}/kill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/mods/<p>/kill` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/mods/${modId}/restore (apps/control-plane/test/analytics.test.ts:118)
`apps/control-plane/test/analytics.test.ts:118` calls `POST /v1/apps/app1/mods/${modId}/restore` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/mods/<p>/restore` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/mods/${modId}/restore (apps/control-plane/test/analytics.test.ts:179)
`apps/control-plane/test/analytics.test.ts:179` calls `POST /v1/apps/app1/mods/${modId}/restore` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/mods/<p>/restore` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/bundles (apps/control-plane/test/analytics.test.ts:130)
`apps/control-plane/test/analytics.test.ts:130` calls `POST /v1/apps/app1/subjects/u1/bundles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/bundles` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/bundles (apps/control-plane/test/analytics.test.ts:141)
`apps/control-plane/test/analytics.test.ts:141` calls `POST /v1/apps/app1/subjects/u1/bundles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/bundles` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/bundles (apps/control-plane/test/analytics.test.ts:56)
`apps/control-plane/test/analytics.test.ts:56` calls `POST /v1/apps/app1/subjects/u1/bundles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/bundles` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/prompts (apps/control-plane/test/authoring.test.ts:185)
`apps/control-plane/test/authoring.test.ts:185` calls `POST /v1/apps/app1/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/prompts` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/prompts (apps/control-plane/test/authoring.test.ts:204)
`apps/control-plane/test/authoring.test.ts:204` calls `POST /v1/apps/app1/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/prompts` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/prompts (apps/control-plane/test/authoring.test.ts:219)
`apps/control-plane/test/authoring.test.ts:219` calls `POST /v1/apps/app1/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/prompts` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/prompts (apps/control-plane/test/design-authoring.test.ts:45)
`apps/control-plane/test/design-authoring.test.ts:45` calls `POST /v1/apps/app1/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/prompts` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/app1/subjects/u1/prompts (apps/control-plane/test/design-authoring.test.ts:80)
`apps/control-plane/test/design-authoring.test.ts:80` calls `POST /v1/apps/app1/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/app1/subjects/u1/prompts` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/demo/manifest (apps/control-plane/scripts/live-design.ts:32)
`apps/control-plane/scripts/live-design.ts:32` calls `POST /v1/apps/demo/manifest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/demo/manifest` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/apps/demo/subjects/u1/prompts (apps/control-plane/scripts/live-design.ts:42)
`apps/control-plane/scripts/live-design.ts:42` calls `POST /v1/apps/demo/subjects/u1/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/demo/subjects/u1/prompts` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (apps/nebula/src/app/api/llm/v1/messages/route.ts:44)
`apps/nebula/src/app/api/llm/v1/messages/route.ts:44` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (packages/cli/src/llm.ts:49)
`packages/cli/src/llm.ts:49` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with …
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/nebula/src/app/layout.tsx:70
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/react/index.tsx:125
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/design-schema/src/css-token-value.ts:5
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/design/src/runtime/ssr.ts:21
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/console/src/api.ts:108
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 — apps/control-plane/src/modules/authoring/anthropic.ts:27
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 — apps/control-plane/src/modules/authoring/openai-compat.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 — apps/control-plane/test/design-config-route.test.ts:7
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 — apps/control-plane/test/events-route.test.ts:16
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 — apps/control-plane/test/themes-route.test.ts:13
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 — apps/control-plane/test/verification.test.ts:240
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 — apps/demo/scripts/seed.ts:7
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 — apps/demo/src/App.tsx:40
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 — apps/demo/test/guardrails-catalog.e2e.test.ts:49
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 — apps/demo/test/helpers.ts:34
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 — apps/demo/test/phase2.e2e.test.ts:34
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 — apps/demo/test/phase4.e2e.test.ts:100
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 — apps/demo/test/phase5.e2e.test.ts:60
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 — apps/nebula/scripts/seed.mjs:9
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/cli/src/cli.ts:67
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/cli/src/llm.ts:24
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/cli/test/cli.test.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 — packages/client/src/core/authoring.ts:15
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/client/src/core/loader.ts:33
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/src/runtime.ts:120
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/middleware.test.ts:147
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/runtime-no-store.test.ts:10
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 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/control-plane/src/app.ts:133
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/control-plane/src/app.ts:133 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/nebula/src/app/layout.tsx:70
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/nebula/src/app/layout.tsx:70 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/react/index.tsx:125
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/react/index.tsx:125 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/core/sanitize.ts:46
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/core/sanitize.ts:46 Direct innerhtml assignment
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 11 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 Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated 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 30 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: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.
Dockerfile:5 containersPinned dependencies
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: apps/console/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/console/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/control-plane/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/control-plane/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/demo/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/demo/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/nebula/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/nebula/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/client/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/client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/design-schema/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/design-schema/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/design/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/design/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/schema/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/schema/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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/control-plane/scripts/live-design.ts:38
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/control-plane/src/main.ts:20
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/demo/scripts/seed.ts:12
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/demo/server/main.ts:15
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/cli/src/cli.ts:158
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: GET /v1/apps/:appId/analytics/summary
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/analytics/summary` 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 /v1/apps/:appId/bundles/:hash
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/bundles/:hash` 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 /v1/apps/:appId/design-config
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/design-config` 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 /v1/apps/:appId/events
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/events` 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 /v1/apps/:appId/manifest
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/manifest` 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 /v1/apps/:appId/mods
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/mods` 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 /v1/apps/:appId/signing-key
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/signing-key` 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 /v1/apps/:appId/subjects/:subjectId/overview
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/subjects/:subjectId/overview` 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 /v1/apps/:appId/subjects/:subjectId/pointer
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/subjects/:subjectId/pointer` 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 /v1/apps/:appId/themes
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/themes` 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 /v1/apps/:appId/themes/history
`apps/control-plane/src/app.ts` declares `GET /v1/apps/:appId/themes/history` 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 /v1/apps/:appId/events
`apps/control-plane/src/app.ts` declares `POST /v1/apps/:appId/events` 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 /v1/apps/:appId/manifest
`apps/control-plane/src/app.ts` declares `POST /v1/apps/:appId/manifest` 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 /v1/apps/:appId/subjects/:subjectId/prompts
`apps/control-plane/src/app.ts` declares `POST /v1/apps/:appId/subjects/:subjectId/prompts` 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: POST /v1/apps/:appId/subjects/:subjectId/refix
`apps/control-plane/src/app.ts` declares `POST /v1/apps/:appId/subjects/:subjectId/refix` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/apps/:appId/subjects/:subjectId/revalidate
`apps/control-plane/src/app.ts` declares `POST /v1/apps/:appId/subjects/:subjectId/revalidate` 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: PUT /v1/apps/:appId/themes
`apps/control-plane/src/app.ts` declares `PUT /v1/apps/:appId/themes` 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 quality Complexity conf 1.00 Very large file: apps/console/src/App.tsx (1517 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/71ba199a-0e11-4e7d-bf03-83c9dd3a2206/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/71ba199a-0e11-4e7d-bf03-83c9dd3a2206/

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.