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

Systemsaholic/nexaas

https://github.com/Systemsaholic/nexaas · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

289 raw signals (147 security + 142 graph)

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

Complete repo analysis

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

JSON
Combined
63.1
/100
Security checks
63
9 findings
System graph
63
100.0% cov · 142 findings
Critical
3
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 3 High 15 Medium 40 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 142 Crowd 0 Layer: Quality 62 Security 24 Frontend 38 Cicd 1 Api 26
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.1/100 with 100.0% coverage. It contains 991 nodes across 16 cross-layer flows, written primarily in mixed languages. Engine surfaced 142 findings — concentrated in quality (54), frontend (38), api (26). Risk profile is high: 1 critical, 11 high, 37 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 124 of 151 actionable findings. 379 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks quality Practices conf 0.82 13 occurrences Foundry mined mock as real or placeholder: Systemsaholic/nexaas
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
13 occurrences
repo-level (13 hits)
critical Security checks security auth conf 0.78 27 occurrences Foundry mined security auth guardrail gaps: Systemsaholic/nexaas
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
27 occurrences
repo-level (27 hits)
critical System graph security Secrets conf 1.00 Possible secret in packages/cli/src/conformance.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
packages/cli/src/conformance.ts:340
high Security checks quality Practices conf 0.84 8 occurrences Foundry mined bad chains: Systemsaholic/nexaas
Comment chain pattern product: bad_chains Repo: Systemsaholic/nexaas Thread: Systemsaholic/nexaas#8 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_gr…
8 occurrences
repo-level (8 hits)
high Security checks quality Practices conf 0.80 3 occurrences Foundry mined docs only runtime fix: Systemsaholic/nexaas
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: supported_by_ve…
3 occurrences
repo-level (3 hits)
high Security checks quality Quality conf 0.76 46 occurrences Foundry mined schema ui api mismatch: Systemsaholic/nexaas
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_high_confidence_link Rep…
46 occurrences
repo-level (46 hits)
high Security checks quality Testing conf 0.78 10 occurrences Foundry mined test ci gap after feedback: Systemsaholic/nexaas
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
10 occurrences
repo-level (10 hits)
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (packages/cli/src/health.ts:71)
`packages/cli/src/health.ts:71` 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 wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (packages/cli/src/status.ts:22)
`packages/cli/src/status.ts:22` 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 wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (packages/runtime/src/tasks/health-monitor.ts:147)
`packages/runtime/src/tasks/health-monitor.ts:147` 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 externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (packages/cli/src/alerts.ts:87)
`packages/cli/src/alerts.ts:87` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (packages/runtime/src/notifications.ts:114)
`packages/runtime/src/notifications.ts:114` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${config.telegram.botToken}/sendMessage (packages/runtime/src/notifications.ts:101)
`packages/runtime/src/notifications.ts:101` calls `POST https://api.telegram.org/bot${config.telegram.botToken}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${process.env.TELEGRAM_BOT_TOKEN}/sendMessage (packages/cli/src/alerts.ts:66)
`packages/cli/src/alerts.ts:66` calls `POST https://api.telegram.org/bot${process.env.TELEGRAM_BOT_TOKEN}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendChatAction (packages/runtime/src/pa/telegram-adapter.ts:66)
`packages/runtime/src/pa/telegram-adapter.ts:66` calls `POST https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendChatAction` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendchata…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage (packages/runtime/src/pa/telegram-adapter.ts:31)
`packages/runtime/src/pa/telegram-adapter.ts:31` calls `POST https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.voyageai.com/v1/embeddings (packages/runtime/src/ingest/embedder.ts:18)
`packages/runtime/src/ingest/embedder.ts:18` calls `POST https://api.voyageai.com/v1/embeddings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.voyageai.com/v1/embeddings` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.voyageai.com/v1/embeddings (packages/runtime/src/rag/retrieve.ts:34)
`packages/runtime/src/rag/retrieve.ts:34` calls `POST https://api.voyageai.com/v1/embeddings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.voyageai.com/v1/embeddings` If this points at an external API, …
Dangling fetchFetch
medium Security checks quality Practices conf 0.62 50 occurrences Foundry mined assumption checks: Systemsaholic/nexaas
Comment chain pattern product: assumption_checks Repo: Systemsaholic/nexaas Thread: Systemsaholic/nexaas#96 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, sour…
50 occurrences
repo-level (50 hits)
medium Security checks quality maintenance conf 0.70 68 occurrences Foundry mined blueprint gap alignment: Systemsaholic/nexaas
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: …
68 occurrences
repo-level (68 hits)
medium Security checks quality Practices conf 0.70 12 occurrences Foundry mined unresolved feedback: Systemsaholic/nexaas
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…
12 occurrences
repo-level (12 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — integrations/email-provider-postmark/src/index.ts:188
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 — integrations/email-provider-resend/src/index.ts:157
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 — integrations/email-provider-sendgrid/src/index.ts:109
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/init.ts:332
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/runtime/src/ingest/embedder.ts:18
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/runtime/src/notifications.ts:101
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/runtime/src/pa/telegram-adapter.ts:31
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/runtime/src/rag/retrieve.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 — scripts/test-email-providers-88.mjs:353
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci, tests, 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'node_child_process' in mcp/servers/webstudio/src/index.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
mcp/servers/webstudio/src/index.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/backup.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/backup.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/config.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/config.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/conformance.ts:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/conformance.ts:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/health.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/health.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/init.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/init.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/library.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/library.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/migrate-flow.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/migrate-flow.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/onboard.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/onboard.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/register-skill.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/register-skill.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/status.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/status.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/upgrade.ts:44
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/upgrade.ts:44 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/ai-skill-verify.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/ai-skill-verify.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/ai-skill.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/ai-skill.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/fleet/heartbeat.ts:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/fleet/heartbeat.ts:34 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/mcp/client.ts:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/mcp/client.ts:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/shell-skill.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/shell-skill.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/tasks/health-monitor.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/tasks/health-monitor.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/webstudio/git-import.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/webstudio/git-import.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/webstudio/publish.ts:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/webstudio/publish.ts:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/runtime/src/worker.ts:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/runtime/src/worker.ts:27 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 44 placeholder/mock markers across 15 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 Integrity conf 1.00 41 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_BASE_URL`, `AUTH_SECRET`, `DASHBOARD_BASE_URL`, `EMAIL_OUTBOUND_PROVIDER`, `HOME`, `NEXAAS_ALLOW_DEV_LAUNCH`, `NEXAAS_CHANNEL`, `NEXAAS_CHUNK_IDLE_MS` + 33 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 698 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: integrations/email-provider-postmark/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.
integrations/email-provider-postmark/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: integrations/email-provider-resend/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.
integrations/email-provider-resend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: integrations/email-provider-sendgrid/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.
integrations/email-provider-sendgrid/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: mcp/servers/palace/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.
mcp/servers/palace/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: mcp/servers/webstudio/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.
mcp/servers/webstudio/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/factory/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/factory/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/integration-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/integration-sdk/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ops-console-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/ops-console-core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/palace/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/palace/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: 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.
packages/runtime/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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/alerts.ts:36
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/backup.ts:49
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/config.ts:40
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/conformance.ts:104
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/create-mcp.ts:17
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/doctor-locks.ts:236
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/dry-run.ts:39
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/gdpr.ts:35
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/health.ts:25
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/index.ts:86
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/init.ts:30
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/library.ts:44
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/migrate-flow.ts:93
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/migration-state.ts:117
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/onboard.ts:338
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/propagate.ts:49
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/register-skill.ts:565
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/register-skills.ts:135
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/seed-palace.ts:194
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/status.ts:52
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/trigger-skill.ts:51
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/upgrade.ts:113
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/validate-manifest.ts:32
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/verify-wal.ts:55
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/runtime/src/ai-skill.ts:217
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/runtime/src/bullmq/connection.ts:24
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/runtime/src/bullmq/rate-limit.ts:112
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/runtime/src/bullmq/worker.ts:229
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/runtime/src/pa/telegram-adapter.ts:91
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/runtime/src/tasks/approval-resolver.ts:384
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/runtime/src/tasks/batch-dispatcher.ts:561
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/runtime/src/tasks/inbound-dispatcher.ts:327
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/runtime/src/tasks/notification-dispatcher.ts:740
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/runtime/src/tasks/output-staleness-watchdog.ts:262
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/runtime/src/tasks/scheduler-watchdog.ts:226
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/runtime/src/tasks/spend-budget-monitor.ts:143
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/runtime/src/worker.ts:352
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: DELETE /api/waitpoints/:id
`packages/runtime/src/worker.ts` declares `DELETE /api/waitpoints/:id` 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 /api/waitpoints/:id
`packages/runtime/src/worker.ts` declares `GET /api/waitpoints/:id` 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 /api/waitpoints/inbound-match/patterns
`packages/runtime/src/worker.ts` declares `GET /api/waitpoints/inbound-match/patterns` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /queues*
`packages/runtime/src/worker.ts` declares `GET /queues*` 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 /api/addons/activate
`packages/runtime/src/worker.ts` declares `POST /api/addons/activate` 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 /api/drawers/inbound
`packages/runtime/src/worker.ts` declares `POST /api/drawers/inbound` 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 /api/ingest
`packages/runtime/src/worker.ts` declares `POST /api/ingest` 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 /api/pa/:user/notify
`packages/runtime/src/worker.ts` declares `POST /api/pa/:user/notify` 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 /api/pa/message
`packages/runtime/src/worker.ts` declares `POST /api/pa/message` 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 /api/skills/trigger
`packages/runtime/src/worker.ts` declares `POST /api/skills/trigger` 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 /api/waitpoints/inbound-match
`packages/runtime/src/worker.ts` declares `POST /api/waitpoints/inbound-match` 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 /api/webstudio/edit
`packages/runtime/src/worker.ts` declares `POST /api/webstudio/edit` 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 /api/webstudio/import
`packages/runtime/src/worker.ts` declares `POST /api/webstudio/import` 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 /api/webstudio/publish
`packages/runtime/src/worker.ts` declares `POST /api/webstudio/publish` 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 /queues
`packages/runtime/src/worker.ts` declares `USE /queues` 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: packages/runtime/src/worker.ts (1352 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/2c598bbd-1219-4e29-b5f9-98ba65f25388/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2c598bbd-1219-4e29-b5f9-98ba65f25388/

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.