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

VerhexIO/deckent-develop

https://github.com/VerhexIO/deckent-develop · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

658 raw signals (0 security + 658 graph)

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

Complete repo analysis

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

JSON
Combined
56.4
/100
Security checks
56
0 findings
System graph
56
100.0% cov · 638 findings
Critical
2
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 2 High 7 Medium 134 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 638 Crowd 0 Layer: Api 1 Frontend 35 Network 2 Hardware 2 Security 104 Cicd 3 Quality 491
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 56.4/100 with 100.0% coverage. It contains 11397 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 658 findings — concentrated in quality (492), security (105), frontend (35). Risk profile is high: 3 critical, 7 high, 137 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 211 of 638 actionable findings. 658 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 System graph security Secrets conf 1.00 Possible secret in docs/audits/sprint-167/oss-whitelist.json
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
docs/audits/sprint-167/oss-whitelist.json:65
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in scripts/auth-mode-resolution-smoke.mjs
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 104, 119
scripts/auth-mode-resolution-smoke.mjs:104, 119 (2 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: deckent-hub/skills/calendar-google/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
deckent-hub/skills/calendar-google/SKILL.md:16 SecretsSkill file
high System graph security security conf 1.00 Insecure pattern 'eval_used' in deckent-hub/README.md:102
Found a known-risky pattern (eval_used). Review and replace if possible.
deckent-hub/README.md:102 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in scripts/hub-validate.mjs:44
Found a known-risky pattern (eval_used). Review and replace if possible.
scripts/hub-validate.mjs:44 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/core/marketplace/skill-sandbox.ts:32
Found a known-risky pattern (eval_used). Review and replace if possible.
src/core/marketplace/skill-sandbox.ts:32 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in scripts/hub-validate.mjs:50
Found a known-risky pattern (exec_used). Review and replace if possible.
scripts/hub-validate.mjs:50 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in deckent-hub/README.md:102
Found a known-risky pattern (new_function_used). Review and replace if possible.
deckent-hub/README.md:102 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in scripts/hub-validate.mjs:45
Found a known-risky pattern (new_function_used). Review and replace if possible.
scripts/hub-validate.mjs:45 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/dashboard-e2e-smoke.mjs:164
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/rt-latency-verify.mjs:90
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/serve-localhost-smoke.mjs:46
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 — src/agents/agentic-worker-runner.ts:275
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 — src/api/oidc-callback-endpoint.ts:273
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 — src/api/terminal/auth-provider.ts:74
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 — src/cli/commands/chat-provider-parity.ts:14
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 — src/connectors/discord.ts:65
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 — src/core/capability-handlers.ts:103
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 — src/core/pricing-updater.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/siem-transport-http.ts:8
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 — src/dashboard/src/lib/api.ts:55
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 — src/dashboard/src/lib/terminal-api.ts: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 — src/dashboard/src/lib/use-live-data.ts:47
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 — src/dashboard/src/pages/LoginPage.tsx:14
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 — src/providers/gemini.ts:614
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 — src/providers/ollama.ts:223
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 — src/providers/openai-compatible.ts:80
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/settings.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.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: AGENTS.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.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/discord-moderator/SKILL.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.
deckent-hub/skills/discord-moderator/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/file-organizer/SKILL.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.
deckent-hub/skills/file-organizer/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/notion-sync/SKILL.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.
deckent-hub/skills/notion-sync/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/screenshot-vision/SKILL.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.
deckent-hub/skills/screenshot-vision/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/slack-notifier/SKILL.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.
deckent-hub/skills/slack-notifier/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/spotify-playlist/SKILL.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.
deckent-hub/skills/spotify-playlist/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/telegram-bot/SKILL.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.
deckent-hub/skills/telegram-bot/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/translator/SKILL.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.
deckent-hub/skills/translator/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: deckent-hub/skills/youtube-downloader/SKILL.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.
deckent-hub/skills/youtube-downloader/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: GEMINI.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.
GEMINI.md VerificationGemini 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 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 quality Integrity conf 1.00 2 occurrences Frontend route `/login` has no Link/navigate to it — src/dashboard/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
2 occurrences
repo-level (2 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:65 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/docs.yml
.github/workflows/publish.yml
.github/workflows/release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/api/output-stream.ts:94
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/api/output-stream.ts:94 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in deckent-hub/skills/youtube-downloader/SKILL.md:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
deckent-hub/skills/youtube-downloader/SKILL.md:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/agentic-do-verify.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/agentic-do-verify.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/audit-user-surfaces.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/audit-user-surfaces.mjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/autonomous-smoke.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/autonomous-smoke.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/beta-launch-precheck.mjs:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/beta-launch-precheck.mjs:27 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-dashboard.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-dashboard.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-verify.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-verify.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/chain-gate-check.mjs:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/chain-gate-check.mjs:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/clean-clone-smoke.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/clean-clone-smoke.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dead-code-audit.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dead-code-audit.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/doc-review.mjs:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/doc-review.mjs:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/pre-flight-health-check.mjs:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/pre-flight-health-check.mjs:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/prepublish.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/prepublish.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/repl-smoke-verify.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/repl-smoke-verify.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/rt-latency-verify.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/rt-latency-verify.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-e2e-harness.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-e2e-harness.mjs:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/security/secret-baseline.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/security/secret-baseline.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/sync-manifest.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/sync-manifest.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/sync-to-product.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/sync-to-product.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/validate-publish.mjs:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/validate-publish.mjs:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/validate-publish.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/validate-publish.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-gitignore.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-gitignore.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/agentic-worker-entry.ts:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/agents/agentic-worker-entry.ts:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/worker-ipc.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/agents/worker-ipc.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/worker-rollback.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/agents/worker-rollback.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/worker-verify.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/agents/worker-verify.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/worker.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/agents/worker.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/api/sprint-job-runner.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/api/sprint-job-runner.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/attach.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/attach.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat-enterprise-bridge.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat-enterprise-bridge.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat-native.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat-native.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat-session.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat-session.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat-tool-bridge.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat-tool-bridge.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat-tool-exec.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat-tool-exec.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/chat.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/chat.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/cleanup.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/cleanup.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/doctor-checks.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/doctor-checks.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/doctor.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/doctor.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/onboard.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/onboard.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/plugin.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/plugin.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/skill.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/skill.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/start.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/start.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/sync.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/sync.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/upgrade.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/upgrade.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/watch.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands/watch.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/helpers/mcp-attach.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/helpers/mcp-attach.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/helpers/wizard.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/helpers/wizard.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/version-info.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/version-info.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/connectors/bot-daemon.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/connectors/bot-daemon.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/analyzer.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/analyzer.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/capability-handlers.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/capability-handlers.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/deck-file.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/deck-file.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/output-collector.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/output-collector.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/plugin-hooks.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/plugin-hooks.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/plugin.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/plugin.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/provider-auth-probe.ts:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/provider-auth-probe.ts:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/provider.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/provider.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/provisioner.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/provisioner.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/subscription.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/subscription.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/system-capacity.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/system-capacity.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/worker-image-check.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/worker-image-check.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/mcp/tools/start.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/mcp/tools/start.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/monitor/auditor.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/monitor/auditor.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/baseline-tracker.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/baseline-tracker.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/disk-verify.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/disk-verify.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/heartbeat-daemon.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/heartbeat-daemon.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/honest-gate.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/honest-gate.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/mid-sprint-adapter.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/mid-sprint-adapter.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/monitor-adapter.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/monitor-adapter.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/planner.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/planner.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/proof-of-function.ts:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/proof-of-function.ts:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/resource-monitor.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/resource-monitor.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/rollback.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/rollback.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/spawn-backend-docker.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/spawn-backend-docker.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/spawn-backend.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/spawn-backend.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/sprint-docs-updater.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/sprint-docs-updater.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/sprint-finalizer.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/sprint-finalizer.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/sprint-planner.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/sprint-planner.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/task-restoration.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/task-restoration.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/timeout-watcher.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/timeout-watcher.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/tmux.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/tmux.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/orchestra/worker-liveness.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/orchestra/worker-liveness.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/claude.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/claude.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/codex.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/codex.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/gemini.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/gemini.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/ollama.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/ollama.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/sandbox.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/sandbox.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/providers/subprocess.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/providers/subprocess.ts:5 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 185 placeholder/mock markers across 86 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 network Security conf 1.00 Privileged port 587 in use
Port 587 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
deckent-hub/skills/email-imap/SKILL.md Ports
medium System graph network Security conf 1.00 Privileged port 993 in use
Port 993 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
deckent-hub/skills/email-imap/SKILL.md Ports
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 Maintenance conf 1.00 43 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1422 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:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 17 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 17 locations
.github/workflows/dashboard-build.yml:43, 46, 86, 100, 103 (5 hits)
.github/workflows/docs.yml:29, 34, 62, 78 (4 hits)
.github/workflows/release.yml:18, 23, 79 (3 hits)
.github/workflows/publish.yml:21, 24 (2 hits)
deckent-hub/.github/workflows/validate-skill.yml:16, 21 (2 hits)
.github/workflows/ci.yml:215
CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/quickstart/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.
examples/quickstart/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: extensions/vscode/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.
extensions/vscode/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `allDeprecated` in scripts/sync-manifest.mjs:160
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cleanOrphanIpcDirsLegacy` in src/core/orphan-cleaner.ts:299
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cleanOrphanIpcDirsLegacy` in tests/core/orphan-cleaner-ipc.test.ts:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `decisionsLegacy` in scripts/adr-validator.mjs:167
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `filter_deprecated` in src/dashboard/src/i18n/en.ts:564
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `filter_deprecated` in src/dashboard/src/i18n/tr.ts:566
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `filter_deprecated` in src/dashboard/src/pages/MemoryExplorerPage.tsx:134
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_prices_and_context_window_backup` in src/core/pricing-updater.ts:61
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `nOld` in tests/orchestra/brain.test.ts:2627
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `nOld` in tests/orchestra/doc-updaters/sprint-log.test.ts:106
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `nOld` in tests/orchestra/managed-docs/managed-doc-runner.test.ts:90
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `src__old` in tests/core/file-lock.test.ts:144
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `src__old` in tests/integration/lifecycle.test.ts:454
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `src__old` in tests/orchestra/preflight-cleanup.test.ts:90
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/close-debt-170-001-fix.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 — scripts/generate-cli-docs.ts:699
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 — scripts/run-self-audit.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 — scripts/validate-publish.ts:472
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 — src/api/server.ts:838
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 — src/cli/commands/bot.ts:46
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 — src/cli/commands/chat-enterprise-bridge.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 — src/cli/commands/evolve.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 — src/cli/commands/features.ts:110
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 — src/cli/commands/sync.ts:469
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 — src/cli/index.ts:81
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 — src/connectors/telegram.ts:9
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 — src/dashboard/src/__tests__/i18n-no-literal-labels.test.tsx:73
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 — src/orchestra/sprint-finalizer.ts:1077
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 — src/orchestra/sprint-phases.ts:668
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 — tests/cli/autonomous-i18n.test.ts:149
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 — tests/cli/chat-render.test.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 — tests/core/marketplace/skill-sandbox.test.ts:387
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 — tests/core/plugin-security.test.ts:78
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 — tests/dashboard/i18n-no-literal-labels.test.tsx:73
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 — tests/load/load-harness.test.ts:149
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 — tests/orchestra/honest-gate-garbage.test.ts:56
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 — tests/orchestra/results-map.test.ts:109
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 — tests/scripts/build-verify.test.ts:82
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 — tests/scripts/validate-publish.test.ts:386
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: src/api/server.ts (1586 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cli/commands/doctor.ts (1621 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cli/helpers/messages.ts (1461 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/core/config.ts (2182 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/monitor/auditor.ts (3059 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/result-collector.ts (1092 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/result-evaluator.ts (2458 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/spawn-backend-docker.ts (1466 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/sprint-controller.ts (1513 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/sprint-finalizer.ts (1580 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/sprint-phases.ts (2283 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/sprint-spawner.ts (1438 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/orchestra/task-builder.ts (1623 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/agents/worker.test.ts (1714 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/api/server.test.ts (1682 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/commands.test.ts (1781 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/commands/doctor.test.ts (2275 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/commands/init.test.ts (2200 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/core/config.test.ts (1382 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/monitor/auditor.test.ts (2897 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/brain.test.ts (2725 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/result-evaluator.test.ts (1476 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/sprint-controller.test.ts (2445 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/sprint-finalizer.test.ts (1357 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/sprint-reporter.test.ts (2349 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/orchestra/task-builder.test.ts (2402 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/f6e30dfd-a9af-491e-9d57-51af25588472/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f6e30dfd-a9af-491e-9d57-51af25588472/

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.