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.

shhashhank/helix

https://github.com/shhashhank/helix · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

160 raw signals (90 security + 70 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 64 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 4 Medium 20 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 6 System graph 64 Crowd 0 Layer: Quality 19 Security 15 Frontend 3 Hardware 1 Api 32

Exclude dismissed / FP Exclude test files

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 60.2/100 with 100.0% coverage. It contains 1738 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 70 findings — concentrated in api (32), security (20), quality (14). Risk profile is high: 9 critical, 2 high, 18 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 56 of 70 actionable findings. 290 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 14 occurrences Foundry mined mock as real or placeholder: shhashhank/helix

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…

14 occurrences

repo-level (14 hits)

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: shhashhank/helix

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…

high Security checks quality Practices conf 0.84 7 occurrences Foundry mined bad chains: shhashhank/helix

Comment chain pattern product: bad_chains Repo: shhashhank/helix Thread: shhashhank/helix#60 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_veri…

7 occurrences

repo-level (7 hits)

high Security checks quality Testing conf 0.78 85 occurrences Foundry mined test ci gap after feedback: shhashhank/helix

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_high_confi…

85 occurrences

repo-level (85 hits)

medium Security checks quality Practices conf 0.62 28 occurrences Foundry mined assumption checks: shhashhank/helix

Comment chain pattern product: assumption_checks Repo: shhashhank/helix Thread: shhashhank/helix#99 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, source_graph…

28 occurrences

repo-level (28 hits)

medium Security checks quality maintenance conf 0.70 85 occurrences Foundry mined blueprint gap alignment: shhashhank/helix

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: …

85 occurrences

repo-level (85 hits)

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — libs/github-mcp/src/app-auth.ts:142

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 — libs/sandbox/src/__tests__/repo-checkout.spec.ts:61

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — libs/sandbox/src/repo-checkout.ts:32

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/skills/helix-merge/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.

.claude/skills/helix-merge/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license. 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 Frontend route `/requests/:id` has no Link/navigate to it — apps/web/src/app/pages/__tests__/run-detail.spec.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.

Orphan pageWiring

medium System graph quality Integrity conf 1.00 Frontend route `/secret` has no Link/navigate to it — apps/web/src/auth/__tests__/auth-context.spec.tsx

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in libs/sandbox/src/command-runner.ts:9

Found a known-risky pattern (node_child_process). Review and replace if possible.

libs/sandbox/src/command-runner.ts:9 Node child process

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 17 placeholder/mock markers across 12 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph quality Integrity conf 1.00 17 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `AUTH_OIDC_AUDIENCE`, `AUTH_OIDC_ISSUER`, `AUTH_OIDC_SECRET`, `AUTH_SESSION_SECRET`, `AUTH_SESSION_TTL_SECONDS`, `CORS_ORIGIN`, `GITHUB_APP_SLUG`, `ORCHESTRATOR_PORT` + 9 more. Add them (with a placeholder/comment) to .env.example so onboarding doe…

config drift

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 7 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 License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality 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 — libs/coding-agent/src/lib/__tests__/workspace-populate.spec.ts:47

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 — libs/sandbox/src/__tests__/repo-checkout.spec.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 — libs/workflow/src/dev-worker.ts:57

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 /${n.pluralKebab}/:id

`libs/coding-agent/src/lib/templates/nest-crud.ts` declares `DELETE /${n.pluralKebab}/: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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /agents/:id

`apps/registry/src/agent-definition/agent-definition.controller.ts` declares `DELETE /agents/: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 documenti…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /approval-policies/:id

`apps/registry/src/approval-policy/approval-policy.controller.ts` declares `DELETE /approval-policies/: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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /${n.pluralKebab}/:id

`libs/coding-agent/src/lib/templates/nest-crud.ts` declares `GET /${n.pluralKebab}/: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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /agents/:id

`apps/registry/src/agent-definition/agent-definition.controller.ts` declares `GET /agents/: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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /agents/latest

`apps/registry/src/agent-definition/agent-definition.controller.ts` declares `GET /agents/latest` 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 documenti…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /approval-policies/:id

`apps/registry/src/approval-policy/approval-policy.controller.ts` declares `GET /approval-policies/: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 doc…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /approval-policies/latest

`apps/registry/src/approval-policy/approval-policy.controller.ts` declares `GET /approval-policies/latest` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /approvals/:id

`apps/orchestrator/src/approval/approval.controller.ts` declares `GET /approvals/: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 consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /approvals/inbox

`apps/orchestrator/src/approval/approval.controller.ts` declares `GET /approvals/inbox` 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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /audit/export

`apps/orchestrator/src/approval/audit.controller.ts` declares `GET /audit/export` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /audit/verify

`apps/orchestrator/src/approval/audit.controller.ts` declares `GET /audit/verify` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/admin/ping

`apps/orchestrator/src/auth/auth.controller.ts` declares `GET /auth/admin/ping` 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 /auth/me

`apps/orchestrator/src/auth/auth.controller.ts` declares `GET /auth/me` 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 /requests/:id

`apps/orchestrator/src/request/request.controller.ts` declares `GET /requests/: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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /requests/:id/artifacts

`apps/orchestrator/src/request/request.controller.ts` declares `GET /requests/:id/artifacts` 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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /requests/:id/run

`apps/orchestrator/src/request/request.controller.ts` declares `GET /requests/:id/run` 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 /requests/overview

`apps/orchestrator/src/request/request.controller.ts` declares `GET /requests/overview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /runs/:id

`apps/orchestrator/src/workflow-run/workflow-run.controller.ts` declares `GET /runs/: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 co…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /${n.pluralKebab}/:id

`libs/coding-agent/src/lib/templates/nest-crud.ts` declares `PATCH /${n.pluralKebab}/: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 c…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /approvals/:id/cancel

`apps/orchestrator/src/approval/approval.controller.ts` declares `POST /approvals/:id/cancel` 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 w…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /approvals/:id/decisions

`apps/orchestrator/src/approval/approval.controller.ts` declares `POST /approvals/:id/decisions` 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 documentin…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /approvals/escalate-due

`apps/orchestrator/src/approval/approval.controller.ts` declares `POST /approvals/escalate-due` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/dev-login

`apps/orchestrator/src/auth/auth.controller.ts` declares `POST /auth/dev-login` 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 /auth/session

`apps/orchestrator/src/auth/auth.controller.ts` declares `POST /auth/session` 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 /integrations/github/callback

`apps/orchestrator/src/integration/github-integration.controller.ts` declares `POST /integrations/github/callback` 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 remo…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/github/connect

`apps/orchestrator/src/integration/github-integration.controller.ts` declares `POST /integrations/github/connect` 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 remov…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/github/test

`apps/orchestrator/src/integration/github-integration.controller.ts` declares `POST /integrations/github/test` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /runs/:id/cancel

`apps/orchestrator/src/workflow-run/workflow-run.controller.ts` declares `POST /runs/:id/cancel` 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 documentin…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /runs/:id/retry

`apps/orchestrator/src/workflow-run/workflow-run.controller.ts` declares `POST /runs/:id/retry` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /agents/:id

`apps/registry/src/agent-definition/agent-definition.controller.ts` declares `PUT /agents/: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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /approval-policies/:id

`apps/registry/src/approval-policy/approval-policy.controller.ts` declares `PUT /approval-policies/: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 doc…

Unused endpoint

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/20137958-0a00-4bd5-b6fc-6fc34a7acf07/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/20137958-0a00-4bd5-b6fc-6fc34a7acf07/

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.